Triple
T20442280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N13 highway |
E501424
|
entity |
| Predicate | hasRouteNumber |
P1864
|
FINISHED |
| Object | N13 |
—
|
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: N13 | Statement: [N13 highway, hasRouteNumber, N13]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: N13 Context triple: [N13 highway, hasRouteNumber, N13]
-
A.
N13
chosen
N13 is a designated national road route identified by the number 13 within a country's highway network.
-
B.
N10
N10 is a numbered national route that intersects with South Africa’s major National Route N2 as part of the country’s primary road network.
-
C.
N12
N12 is a national highway designation used for a major numbered route within a country's road network.
-
D.
N14
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.
-
E.
N1
N1 is a major national highway route, typically serving as a primary north–south or intercity transport corridor in the country’s road network.
- 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_69e0b4ac0a1c81908845d0f8a56abce8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e685f3b794819080745b135a305ba7 |
completed | April 20, 2026, 8 p.m. |
Created at: April 16, 2026, 11:32 a.m.