Triple
T22628374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Đông Hà |
E558483
|
entity |
| Predicate | distanceToDMZ |
P31353
|
FINISHED |
| Object | approximately 10 kilometers south of the former DMZ |
—
|
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 kilometers south of the former DMZ | Statement: [Đông Hà, distanceToDMZ, approximately 10 kilometers south of the former DMZ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToDMZ Context triple: [Đông Hà, distanceToDMZ, approximately 10 kilometers south of the former DMZ]
-
A.
distanceToBorder
chosen
Indicates the measured or estimated spatial separation between a given entity or location and the nearest relevant border or boundary.
-
B.
distanceFromDowntown
Indicates the physical distance between a given location and the central downtown area.
-
C.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
-
D.
distanceFromMina
Indicates the spatial distance measured between Mina and another specified entity or location.
-
E.
distanceToBawtry
Indicates the spatial distance between a given entity and the location of Bawtry.
- 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_69e245467d9881908d6985bd0db7a1f1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f16e3ed1d48190a093013d829901b9 |
completed | April 29, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 3:02 p.m.