Triple
T25141457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egelsbach Airfield |
E629811
|
entity |
| Predicate | distanceToFrankfurtCityCentre |
P88078
|
FINISHED |
| Object | approximately 17 km |
—
|
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 17 km | Statement: [Egelsbach Airfield, distanceToFrankfurtCityCentre, approximately 17 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToFrankfurtCityCentre Context triple: [Egelsbach Airfield, distanceToFrankfurtCityCentre, approximately 17 km]
-
A.
distanceToFrankfurtHbf
Indicates the spatial distance between a given location and Frankfurt Hauptbahnhof (Frankfurt Hbf).
-
B.
distanceToFrankfurt
chosen
Indicates the spatial distance between a given location or entity and the city of Frankfurt.
-
C.
distanceToFrankfurtAirport_km
Indicates the physical distance, measured in kilometers, between a given location and Frankfurt Airport.
-
D.
distanceToBerlin
Indicates the spatial distance between a given entity’s location and the city of Berlin.
-
E.
distanceFromHagenHbf_km
Indicates the distance, measured in kilometers, between a given location and Hagen Hauptbahnhof (Hagen central railway station).
- 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 18, 2026, 6:29 a.m.