Triple
T14304246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N14 highway |
E354649
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | N14 |
E969459
|
NE 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: N14 | Statement: [N14 highway, abbreviation, N14]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: N14 Context triple: [N14 highway, abbreviation, 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.
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.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de85afabe48190926d6098047f4bcf |
completed | April 14, 2026, 6:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd3d2a56a4819095b5c2164b1ad9fb |
completed | May 8, 2026, 1:32 a.m. |
Created at: April 10, 2026, 1:12 a.m.