Triple
T4388886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Business Bay Crossing |
E99313
|
entity |
| Predicate | lanesDirection |
P18336
|
FINISHED |
| Object | 7 lanes in one direction |
—
|
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: 7 lanes in one direction | Statement: [Business Bay Crossing, lanesDirection, 7 lanes in one direction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lanesDirection Context triple: [Business Bay Crossing, lanesDirection, 7 lanes in one direction]
-
A.
laneCount
chosen
Indicates the number of parallel lanes associated with a given road or roadway segment.
-
B.
hasTrafficDirection
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
-
C.
hasLanes
Indicates that an entity, such as a road or pathway, is divided into one or more distinct lanes for traffic or movement.
-
D.
hasDedicatedLanes
Indicates that specific lanes within a route or roadway are reserved exclusively for a particular type of traffic or use.
-
E.
hasStreetDirection
Indicates that a street or road segment is associated with a specific directional orientation (e.g., northbound, east-west).
- 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35281900c8190882e9ccfa44ab86f |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f572efc8190bad1e5078cbcb75a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:19 p.m.