Triple
T23143206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South African National Route network |
E577516
|
entity |
| Predicate | includesRoute |
P4374
|
FINISHED |
| Object | N14 |
—
|
NE NERFINISHED |
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: N14 | Statement: [South African National Route network, includesRoute, N14]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: N14 Context triple: [South African National Route network, includesRoute, N14]
-
A.
N14
chosen
N14 is a major national route in South Africa that links Johannesburg with the North West and Northern Cape provinces, serving as an important regional transport corridor.
-
B.
N141
N141 is a French national highway that serves as a major regional route connecting several towns and cities, including Guéret, in central France.
-
C.
N104
N104 is a major ring road in the Île-de-France region, forming part of the Francilienne orbital route around Paris.
-
D.
N13
N13 is a designated national road route identified by the number 13 within a country's highway network.
-
E.
N214
N214 is a regional road in the Netherlands that provides a key connection to the village of Hoornaar and surrounding areas.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245f8e6248190ba3d58e068b4dccb |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18ecc3710819088ac5d72dad0459a |
completed | April 29, 2026, 4:53 a.m. |
Created at: April 17, 2026, 4 p.m.