Triple
T1703631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Via Appia |
E36820
|
entity |
| Predicate | endPoint |
P390
|
FINISHED |
| Object | Brindisi |
E131131
|
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: Brindisi | Statement: [Via Appia, endPoint, Brindisi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brindisi Context triple: [Via Appia, endPoint, Brindisi]
-
A.
Brindisi
chosen
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.
Taranto
Taranto is a historic coastal city in southern Italy known as a major naval and commercial hub and for its strategic position on the Gulf of Taranto.
-
C.
Pescara
Pescara is a coastal city in the Abruzzo region of central Italy, known for its Adriatic beaches, modern urban layout, and role as a commercial and tourist hub.
-
D.
Bari
Bari is a major port city in southern Italy that served as an important Allied military hub and logistics center during World War II.
-
E.
Foggia
Foggia is a city in the Apulia region of southern Italy, historically significant as a medieval center and later as an important agricultural and commercial hub.
- 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_69a88617439c819094ffb5d16a0f6307 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa62f25bac8190977d6f3bd79363cb |
completed | March 6, 2026, 5:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae58af914c8190a27a834e3097bec7 |
completed | March 9, 2026, 5:20 a.m. |
Created at: March 4, 2026, 7:30 p.m.