Triple
T5745649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A73 motorway (Netherlands) |
E126724
|
entity |
| Predicate | roadNumberPrefix |
P66494
|
FINISHED |
| Object | A |
—
|
LITERAL 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: A | Statement: [A73 motorway (Netherlands), roadNumberPrefix, A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadNumberPrefix Context triple: [A73 motorway (Netherlands), roadNumberPrefix, A]
-
A.
routeNumberFormat
Indicates how the identifying number or code for a route is structured or formatted.
-
B.
roadNumberRange
Indicates that a road is identified by a continuous range of road numbers between a specified minimum and maximum.
-
C.
isNumberedStreet
Indicates that a street is designated primarily by a number (e.g., "1st Street," "42nd Avenue") rather than by a proper name.
-
D.
roadNumberingZone
Indicates the designated numbering zone or area within which a particular road’s identification or route number is assigned.
-
E.
routeNumber
Indicates the specific identifying number assigned to a route within a transportation or delivery network.
- F. None of above. chosen
Provenance (4 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_69c0083179548190b384b0bf3c08ca4d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b52663c8190ab44258468d4296d |
completed | March 22, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c021ca61688190875bd6107161c284 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c02b4ea03c81908c3d799462de20c4 |
completed | March 22, 2026, 5:47 p.m. |
Created at: March 22, 2026, 3:48 p.m.