Triple
T35724896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dark Red Line |
E1032581
|
entity |
| Predicate | hasSegregationFromRoadTraffic |
P147880
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Dark Red Line, hasSegregationFromRoadTraffic, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSegregationFromRoadTraffic Context triple: [Dark Red Line, hasSegregationFromRoadTraffic, yes]
-
A.
hasLaneSeparation
chosen
Indicates that there is a physical or marked separation between traffic lanes.
-
B.
hasRightOfWaySeparation
Indicates that one entity is required to maintain a specified right-of-way distance or separation from another entity.
-
C.
hasRoadClass
Indicates that a road segment is assigned to a particular classification or category based on its type or functional importance.
-
D.
hasTrafficControl
Indicates that some form of traffic management or regulation mechanism is present or applied to a given route, intersection, or transportation element.
-
E.
hasCarriagewayRestrictions
Indicates that certain limitations or prohibitions apply to the use or access of a specific carriageway.
- 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00233e2170819084bee0c8f74cc1a4 |
completed | May 10, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_6a0022943fd08190b73007f080d5971d |
completed | May 10, 2026, 6:15 a.m. |
Created at: May 3, 2026, 4:05 p.m.