Triple
T10103179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hadamar |
E216251
|
entity |
| Predicate | distanceToLimburgAnDerLahn |
P92438
|
FINISHED |
| Object | approximately 7 km north |
—
|
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 7 km north | Statement: [Hadamar, distanceToLimburgAnDerLahn, approximately 7 km north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToLimburgAnDerLahn Context triple: [Hadamar, distanceToLimburgAnDerLahn, approximately 7 km north]
-
A.
distanceToWetzlar
Indicates the measured distance between a given entity or location and the place named Wetzlar.
-
B.
distanceToWiesbaden
Indicates the spatial distance between a given entity or location and the city of Wiesbaden.
-
C.
distanceToLuxembourgCityKilometers
Indicates the physical distance, measured in kilometers, between the given entity and Luxembourg City.
-
D.
distanceToEindhovenKmApproximate
Indicates the approximate distance, measured in kilometers, between a given entity and Eindhoven.
-
E.
distanceToRotterdam
Indicates the measured distance between a given entity’s location and the city of Rotterdam.
- 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_69ca83d039f08190b9d10363221c69fb |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd09af07c819099774af46ebf62d7 |
completed | April 2, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9b853c8190a2af993ce9b21309 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd5150ae98819086c4f822114b4e2c |
completed | April 1, 2026, 5:09 p.m. |
Created at: March 30, 2026, 9:03 p.m.