Triple
T3164923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hettange-Grande |
E66187
|
entity |
| Predicate | distanceToLuxembourgCityKm |
P40111
|
FINISHED |
| Object | approximately 20 |
—
|
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 20 | Statement: [Hettange-Grande, distanceToLuxembourgCityKm, approximately 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToLuxembourgCityKm Context triple: [Hettange-Grande, distanceToLuxembourgCityKm, approximately 20]
-
A.
distanceToLuxembourgCityKilometers
chosen
Indicates the physical distance, measured in kilometers, between the given entity and Luxembourg City.
-
B.
distanceToMetzKilometers
Indicates the physical distance, measured in kilometers, between a given entity’s location and the city of Metz.
-
C.
cityDistanceFromBrussels_km
Indicates the distance, measured in kilometers, between a given city and Brussels.
-
D.
distanceFromStrasbourg
Indicates the spatial distance between a given place or entity and the city of Strasbourg.
-
E.
distanceToBudapest_km
Indicates the physical distance, measured in kilometers, between a given location and Budapest.
- 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada6424ee48190a29891ffbbc3811d |
completed | March 8, 2026, 4:39 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfe0a948190928f2201d671c654 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.