Triple
T13542851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halfway House |
E323433
|
entity |
| Predicate | approximateDistanceToJohannesburg |
P110771
|
FINISHED |
| Object | midway |
—
|
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: midway | Statement: [Halfway House, approximateDistanceToJohannesburg, midway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDistanceToJohannesburg Context triple: [Halfway House, approximateDistanceToJohannesburg, midway]
-
A.
distanceToJohannesburg_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and Johannesburg.
-
B.
approximateDistanceFromOudtshoorn
Indicates an estimated or rough measurement of distance from the location Oudtshoorn to another entity.
-
C.
distanceFromPretoria
Indicates the spatial distance between a given entity or location and the city of Pretoria.
-
D.
distanceToDurban_km
Indicates the physical distance, measured in kilometers, between a given location and the city of Durban.
-
E.
distanceToSouthAfrica
Indicates the measured or calculated spatial distance between a given entity and the country of South Africa.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafd8ba10819098faadcc6adf251e |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbaecc98cc8190829f5be759c4f1e3 |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:45 p.m.