Triple
T20857917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 68 |
E513529
|
entity |
| Predicate | laneConfigurationTypical |
P83805
|
FINISHED |
| Object | four-lane divided highway |
—
|
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: four-lane divided highway | Statement: [Interstate 68, laneConfigurationTypical, four-lane divided highway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laneConfigurationTypical Context triple: [Interstate 68, laneConfigurationTypical, four-lane divided highway]
-
A.
typicalLanes
Indicates the usual or standard number or configuration of lanes associated with a road or similar transportation segment.
-
B.
laneStructure
chosen
Indicates the structural organization and configuration of lanes within a roadway or traffic facility.
-
C.
laneCount
Indicates the number of parallel lanes associated with a given road or roadway segment.
-
D.
laneConfigurationChange
Indicates a change in the number, type, or arrangement of lanes along a roadway segment.
-
E.
hasLaneConfigurations
Indicates that an entity is associated with one or more specific arrangements or patterns of lanes (e.g., number, type, or direction of lanes).
- 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_69e0b4f5b01081909452f654d2fc3f50 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c3a9fd7881908ae4c5c63f64efc0 |
completed | April 21, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:44 p.m.