Triple
T20597853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treviso Airport |
E506096
|
entity |
| Predicate | distanceToTrevisoKilometers |
P140714
|
FINISHED |
| Object | approximately 3 |
—
|
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: approximately 3 | Statement: [Treviso Airport, distanceToTrevisoKilometers, approximately 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToTrevisoKilometers Context triple: [Treviso Airport, distanceToTrevisoKilometers, approximately 3]
-
A.
distanceToTrieste
Indicates the measured or calculated distance between a given entity or location and the city of Trieste.
-
B.
distanceToVenice_km
Indicates the physical distance, measured in kilometers, between a given place and the city of Venice.
-
C.
distanceToSavona_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and the city of Savona.
-
D.
distanceFromTerniInKilometers
Indicates the physical distance, measured in kilometers, between a given entity’s location and the city of Terni.
-
E.
distanceToPadua
Indicates the measured distance between a given entity’s location and the city of Padua.
- F. None of above. chosen
Provenance (4 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_69e0b4ba6ae88190af871e1f9522c704 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aa1d15b08190a720fc7cefbf333e |
completed | April 20, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a9f3f88190b961db9aca36f7da |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:40 a.m.