Triple
T22715065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bari–Taranto railway |
E561706
|
entity |
| Predicate | lineNumber |
P1864
|
FINISHED |
| Object |
Taranto–Bari
Taranto–Bari is a key Italian railway line connecting the coastal cities of Taranto and Bari in the Apulia region.
|
E1550325
|
NE FINISHED |
How this triple was built (4 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: Taranto–Bari | Statement: [Bari–Taranto railway, lineNumber, Taranto–Bari]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Taranto–Bari Context triple: [Bari–Taranto railway, lineNumber, Taranto–Bari]
-
A.
Brindisi
Brindisi is a historic port city in southern Italy’s Apulia region, long serving as a key maritime gateway between Italy and the eastern Mediterranean.
-
B.
Nardò
Nardò is a historic town in Italy’s Apulia region, known for its Baroque architecture and location in the province of Lecce in the Salento area.
-
C.
Rome–Palermo
Rome–Palermo was a key domestic air route in Italy connecting the capital city Rome with the Sicilian city of Palermo.
-
D.
Barletta
Barletta is a historic coastal city in the Apulia region of southern Italy, known for its medieval architecture and role as a provincial capital.
-
E.
Naples-Foggia
Naples-Foggia refers to a World War II Allied campaign in southern Italy focused on the liberation and control of the Naples and Foggia regions.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Taranto–Bari Triple: [Bari–Taranto railway, lineNumber, Taranto–Bari]
Generated description
Taranto–Bari is a key Italian railway line connecting the coastal cities of Taranto and Bari in the Apulia region.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Taranto–Bari Target entity description: Taranto–Bari is a key Italian railway line connecting the coastal cities of Taranto and Bari in the Apulia region.
-
A.
Brindisi
Brindisi is a historic port city in southern Italy’s Apulia region, long serving as a key maritime gateway between Italy and the eastern Mediterranean.
-
B.
Nardò
Nardò is a historic town in Italy’s Apulia region, known for its Baroque architecture and location in the province of Lecce in the Salento area.
-
C.
Rome–Palermo
Rome–Palermo was a key domestic air route in Italy connecting the capital city Rome with the Sicilian city of Palermo.
-
D.
Barletta
Barletta is a historic coastal city in the Apulia region of southern Italy, known for its medieval architecture and role as a provincial capital.
-
E.
Naples-Foggia
Naples-Foggia refers to a World War II Allied campaign in southern Italy focused on the liberation and control of the Naples and Foggia regions.
- F. None of above. chosen
Provenance (5 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_69e2454f1348819088d83f420925a5c1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1790ca59881909064d49f331fb711 |
completed | April 29, 2026, 3:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0b7edd69648190af49c198a389798f |
completed | May 18, 2026, 9:04 p.m. |
| NEDg | Description generation | batch_6a0b80627f10819096773bfbc8d8fc76 |
completed | May 18, 2026, 9:10 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0b813421ec8190bdc6e0920ddbf6a5 |
completed | May 18, 2026, 9:14 p.m. |
Created at: April 17, 2026, 3:18 p.m.