Triple
T17599348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salento |
E428653
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Otranto |
—
|
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: Otranto | Statement: [Salento, contains, Otranto]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Otranto Context triple: [Salento, contains, Otranto]
-
A.
Otranto
chosen
Otranto is a historic coastal town in southern Italy’s Apulia region, known for its medieval castle, cathedral, and strategic position on the Adriatic Sea.
-
B.
Durazzo
Durazzo is the historical Italian name for the coastal city of Durrës in present-day Albania, an important Adriatic port that served as a key maritime and commercial hub in various Mediterranean empires.
-
C.
Manfredonia
Manfredonia is a coastal town in Italy’s Apulia region, known for its Adriatic seafront, fishing harbor, and proximity to the Gargano promontory.
-
D.
Lecce
Lecce is a historic city in Italy’s Apulia region, renowned for its rich Baroque architecture and cultural heritage.
-
E.
Avetrana
Avetrana is a small town and comune in the Apulia region of southern Italy, known for its historic center and proximity to the Ionian Sea.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46c474e5481909d2736241b592dab |
completed | April 19, 2026, 5:46 a.m. |
Created at: April 10, 2026, 5:51 a.m.