Triple
T12056439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Route N2 |
E287053
|
entity |
| Predicate | hasJunctionWith |
P1018
|
FINISHED |
| Object | N3 |
E710599
|
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: N3 | Statement: [National Route N2, hasJunctionWith, N3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: N3 Context triple: [National Route N2, hasJunctionWith, N3]
-
A.
N3
chosen
N3 is a Dutch regional road that serves as a key connector route in the South Holland region of the Netherlands.
-
B.
N3/N5
N3/N5 is the U.S. Navy staff directorate responsible for integrating operations, plans, and strategy at the highest levels of naval command.
-
C.
N5
N5 is a major Pakistani national highway that forms part of the country’s primary north–south transport corridor.
-
D.
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.
-
E.
N
The N is a New York City Subway service that runs along the Broadway Line in Manhattan and connects Queens, Manhattan, and Brooklyn.
- 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_69d6ab4780948190bdb9f7620c2ac27e |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9043bf0ec8190a51ef2641808320c |
completed | April 10, 2026, 2:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f49dea043c8190a74ffb448bbae5d0 |
completed | May 1, 2026, 12:34 p.m. |
Created at: April 8, 2026, 9:47 p.m.