Triple
T20216478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N331 |
E495139
|
entity |
| Predicate | hasJunctionWith |
P1018
|
FINISHED |
| Object | N351 road |
—
|
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: N351 road | Statement: [N331, hasJunctionWith, N351 road]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: N351 road Context triple: [N331, hasJunctionWith, N351 road]
-
A.
N351 road
chosen
The N351 road is a regional highway in the Netherlands that connects several towns in the provinces of Friesland and Overijssel.
-
B.
N35 road
The N35 road is a major Dutch regional highway connecting the city of Zwolle with Enschede, running through the Salland region in the province of Overijssel.
-
C.
N31 road
The N31 road is a national primary route in Ireland that connects the port town of Dún Laoghaire with the country’s main road network.
-
D.
N310 road
The N310 road is a regional highway in the Netherlands that connects several towns and rural areas in the central-eastern part of the country.
-
E.
N331 road
The N331 road is a regional Dutch highway connecting several towns in the provinces of Overijssel and Flevoland, serving as an important route between Zwolle and Emmeloord.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66eda2f188190adf39d895e8b99f2 |
completed | April 20, 2026, 6:22 p.m. |
Created at: April 11, 2026, 11:39 p.m.