Triple
T8045142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trevi |
E187528
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Foligno |
E214235
|
NE FINISHED |
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: Foligno | Statement: [Trevi, locatedNear, Foligno]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Foligno Context triple: [Trevi, locatedNear, Foligno]
-
A.
Foligno
chosen
Foligno is a historic city in central Italy known for its medieval architecture, cultural festivals, and strategic location along the Via Flaminia.
-
B.
Fermo
Fermo is a historic hilltop city in Italy’s Marche region, known for its medieval architecture, Roman heritage, and panoramic views over the Adriatic coast.
-
C.
Rieti
Rieti is a historic town in central Italy often considered the geographical center of the country and known for its medieval architecture and proximity to the Apennine Mountains.
-
D.
Terni
Terni is an industrial city in the Umbria region of central Italy, known for its steel production and historic Roman and medieval heritage.
-
E.
Chivasso
Chivasso is a town and comune in the Piedmont region of northwestern Italy, situated near Turin along the Po River.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca82b00cb48190b59a300f70e97bd7 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f4c79388190aecee6e313071a17 |
completed | March 31, 2026, 3:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd946a5e188190b2ef0a07a885ade7 |
completed | April 1, 2026, 9:55 p.m. |
Created at: March 30, 2026, 5:24 p.m.