Triple
T12989082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doetinchem |
E321848
|
entity |
| Predicate | borderDistanceToGermany |
P107919
|
FINISHED |
| Object | approximately 15 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 15 km | Statement: [Doetinchem, borderDistanceToGermany, approximately 15 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderDistanceToGermany Context triple: [Doetinchem, borderDistanceToGermany, approximately 15 km]
-
A.
EUInternalBorder
Indicates that a border lies between two member states within the European Union, where internal EU border rules apply.
-
B.
bordersGermanState
Indicates that one entity shares a land or maritime boundary directly with a German federal state.
-
C.
wasInnerGermanBorder
Indicates that a location or boundary segment functioned as part of the former inner German border separating East and West Germany.
-
D.
borderTypeWithItaly
Indicates the type or nature of the border that an entity shares with Italy.
-
E.
distanceToPolishBorder
Indicates the measured distance between a given location and the nearest point on the border of Poland.
- 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97f2a71a0819098bb6cf8a4b2208a |
completed | April 10, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69d97dbdd94c8190ac4bbecca02dc77b |
completed | April 10, 2026, 10:46 p.m. |
| PDg | Predicate description generation | batch_69d97f1badac8190a59e60751f47b8d6 |
completed | April 10, 2026, 10:52 p.m. |
Created at: April 9, 2026, 8:42 p.m.