Triple
T16338367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSC Bari |
E396732
|
entity |
| Predicate | hasRival |
P1375
|
FINISHED |
| Object | Lecce |
E581355
|
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: Lecce | Statement: [SSC Bari, hasRival, Lecce]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lecce Context triple: [SSC Bari, hasRival, Lecce]
-
A.
Lecce
chosen
Lecce is a historic city in Italy’s Apulia region, renowned for its rich Baroque architecture and cultural heritage.
-
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.
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.
-
D.
Molfetta
Molfetta is a coastal city in the Apulia region of southern Italy, known for its historic old town, fishing port, and Adriatic seaside location.
-
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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4e6338081908aa03ee3dcbe5f70 |
completed | April 17, 2026, 11:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01232399008190b23dfaec237563ef |
completed | May 11, 2026, 12:30 a.m. |
Created at: April 10, 2026, 5:07 a.m.