Triple
T10760348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N366 |
E253809
|
entity |
| Predicate | roadNumber |
P1864
|
FINISHED |
| Object | N366 |
E253809
|
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: N366 | Statement: [N366, roadNumber, N366]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: N366 Context triple: [N366, roadNumber, N366]
-
A.
N366
chosen
N366 is a regional road in the Netherlands that serves as a key connection route for traffic to and from the municipality of Pekela in the province of Groningen.
-
B.
N367
N367 is a regional road in the Netherlands that connects several towns in the province of Groningen, facilitating local and regional traffic.
-
C.
N62
N62 is a major Dutch roadway in the province of Zeeland that connects key transport routes and includes the Westerscheldetunnel under the Western Scheldt.
-
D.
R36
R36 is a regional road in South Africa that connects the town of Lydenburg with other major routes and settlements in the region.
-
E.
R36
R36 is a regional commuter rail line within the Rodalies de Catalunya network serving passengers in Catalonia, Spain.
- 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d731a14c7481909c6f4f9b15dc130f |
completed | April 9, 2026, 4:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69de84b88ba08190afddea2976d12465 |
completed | April 14, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:16 p.m.