Triple
T20075332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinenoord Tunnel |
E499846
|
entity |
| Predicate | numberOfLanesPerDirection |
P18336
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Heinenoord Tunnel, numberOfLanesPerDirection, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfLanesPerDirection Context triple: [Heinenoord Tunnel, numberOfLanesPerDirection, 2]
-
A.
laneCount
chosen
Indicates the number of parallel lanes associated with a given road or roadway segment.
-
B.
hasLanes
Indicates that an entity, such as a road or pathway, is divided into one or more distinct lanes for traffic or movement.
-
C.
numberOfLanesInFinal
Indicates the total count of lanes present in the final stage or configuration of something (e.g., a road, track, or process).
-
D.
typicalLanes
Indicates the usual or standard number or configuration of lanes associated with a road or similar transportation segment.
-
E.
hasDedicatedLanes
Indicates that specific lanes within a route or roadway are reserved exclusively for a particular type of traffic or use.
- F. None of above.
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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6643ab0448190ab18d013b72aaf32 |
completed | April 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:40 p.m.