Triple
T21557013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ennepetal (Gevelsberg) station |
E531918
|
entity |
| Predicate | distanceFromHagenHbf_km |
P144233
|
FINISHED |
| Object | about 15 |
—
|
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: about 15 | Statement: [Ennepetal (Gevelsberg) station, distanceFromHagenHbf_km, about 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromHagenHbf_km Context triple: [Ennepetal (Gevelsberg) station, distanceFromHagenHbf_km, about 15]
-
A.
distanceToFrankfurtHbf
Indicates the spatial distance between a given location and Frankfurt Hauptbahnhof (Frankfurt Hbf).
-
B.
distanceToKoblenz
Indicates the spatial distance between a given entity and the location of Koblenz.
-
C.
distanceToHamburg
Indicates the spatial distance between a given entity’s location and the city of Hamburg.
-
D.
distanceToDortmund
Indicates the spatial distance between a given entity’s location and the city of Dortmund.
-
E.
distanceToFrankfurtAirport_km
Indicates the physical distance, measured in kilometers, between a given location and Frankfurt Airport.
- 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eed2e04b048190ac3a9913094b4625 |
completed | April 27, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:29 p.m.