Triple
T12256248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N1 Western Bypass |
E292107
|
entity |
| Predicate | hasRouteNumber |
P1864
|
FINISHED |
| Object | N1 |
E265811
|
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: N1 | Statement: [N1 Western Bypass, hasRouteNumber, N1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: N1 Context triple: [N1 Western Bypass, hasRouteNumber, N1]
-
A.
N1
chosen
N1 is a major national highway route, typically serving as a primary north–south or intercity transport corridor in the country’s road 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.
N
The N is a New York City Subway service that runs along the Broadway Line in Manhattan and connects Queens, Manhattan, and Brooklyn.
-
D.
N2
N2 is a major national highway designated as National Route N2 in its country’s road network.
-
E.
N3
N3 is a Dutch regional road that serves as a key connector route in the South Holland region of the Netherlands.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91cc9dd5081908880061d52351850 |
completed | April 10, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f60abdc5988190a19104385f54fb06 |
completed | May 2, 2026, 2:31 p.m. |
Created at: April 8, 2026, 9:52 p.m.