Triple
T33810259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Badhoevedorp interchange |
E866510
|
entity |
| Predicate | roadNumberA9Direction |
P178115
|
FINISHED |
| Object | Alkmaar |
—
|
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: Alkmaar | Statement: [Badhoevedorp interchange, roadNumberA9Direction, Alkmaar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadNumberA9Direction Context triple: [Badhoevedorp interchange, roadNumberA9Direction, Alkmaar]
-
A.
roadNumberA10Direction
Indicates the direction associated with road number A10 in a given road or traffic context.
-
B.
roadNumberA4Direction
Indicates the directional orientation associated with road number A4, specifying the direction in which that road segment runs or is traveled.
-
C.
routeDirectionA
Indicates the primary or first directional orientation or heading associated with a specific route.
-
D.
isNumberedHighway
Indicates that a roadway is officially designated and signed as a numbered highway within a road network.
-
E.
roadNumberIncludes
Indicates that a road’s identifier or designation contains the specified number or numeric sequence.
- 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70c53062c8190b4cb7be22ab00bc7 |
completed | May 3, 2026, 8:50 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70b94784c8190970d654e066eb50d |
completed | May 3, 2026, 8:47 a.m. |
Created at: May 1, 2026, 1:46 a.m.