Triple
T8797606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taunusstein |
E209327
|
entity |
| Predicate | distanceToWiesbaden |
P84685
|
FINISHED |
| Object | approximately 10–15 kilometres |
—
|
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 10–15 kilometres | Statement: [Taunusstein, distanceToWiesbaden, approximately 10–15 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToWiesbaden Context triple: [Taunusstein, distanceToWiesbaden, approximately 10–15 kilometres]
-
A.
distanceToStuttgart
Indicates the measured distance between a given entity’s location and the city of Stuttgart.
-
B.
distanceToBerlin
Indicates the spatial distance between a given entity’s location and the city of Berlin.
-
C.
distanceToHamburg
Indicates the spatial distance between a given entity’s location and the city of Hamburg.
-
D.
distanceToBremen
Indicates the spatial distance between a given entity and the location of Bremen.
-
E.
distanceToNuremberg
Indicates the spatial distance between a given entity and the location of Nuremberg.
- 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_69ca836240888190a62b262e56a69d2f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fa370d08190885ef65e3a3e56d3 |
completed | March 31, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1d48f08190b325a77d4c76d223 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:44 p.m.