Triple
T24128627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amerigo Vespucci Airport |
E597879
|
entity |
| Predicate | cityCentreDirection |
P26962
|
FINISHED |
| Object | northwest of Florence city centre |
—
|
LITERAL 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: northwest of Florence city centre | Statement: [Amerigo Vespucci Airport, cityCentreDirection, northwest of Florence city centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityCentreDirection Context triple: [Amerigo Vespucci Airport, cityCentreDirection, northwest of Florence city centre]
-
A.
directionFromCityCentre
chosen
Indicates the compass direction in which one location lies relative to the city centre.
-
B.
directionFromCityCenter
Indicates the compass direction in which one location lies relative to the city center.
-
C.
distanceFromCityCenterDirection
Indicates the distance and compass direction of a location relative to the center of a specified city.
-
D.
cityCentreAccess
Indicates whether an entity has access to, or is reachable within, the central area of a city.
-
E.
locationDirection
Indicates that one entity is located in a specific directional relation (such as north, south, above, or below) relative to another entity.
- F. None of above.
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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df751c94819084652a89c7c2cc1f |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:22 p.m.