Triple
T16039868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N3 highway |
E389065
|
entity |
| Predicate | routeNumber |
P1864
|
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: [N3 highway, routeNumber, N3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: N3 Context triple: [N3 highway, routeNumber, 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.
N1
N1 is a central London postcode district covering parts of Islington, Hoxton, and surrounding areas known for their vibrant urban character.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1833f84188190baa3a452df880284 |
completed | April 17, 2026, 12:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffdbd77c5481908644742a8a8f3e68 |
completed | May 10, 2026, 1:13 a.m. |
Created at: April 10, 2026, 4:56 a.m.