Triple
T30167318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comune di Modena |
E766829
|
entity |
| Predicate | regionallyLocatedIn |
P64798
|
FINISHED |
| Object | northern Italy |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: northern Italy | Statement: [Comune di Modena, regionallyLocatedIn, northern Italy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionallyLocatedIn Context triple: [Comune di Modena, regionallyLocatedIn, northern Italy]
-
A.
regionallyAssociatedWith
Indicates that two entities are connected or related based on sharing the same or overlapping geographic or regional context.
-
B.
locatedInStateOrRegion
Indicates that one entity is geographically situated within the boundaries of a specified state or region.
-
C.
regionSeatLocatedIn
Indicates that the administrative seat or capital of a region is located within that region.
-
D.
placeRegion
chosen
Indicates that a place is located within, or is part of, a larger geographic or administrative region.
-
E.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: April 29, 2026, 7:23 p.m.