Triple
T29065543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brock (M20 barrier system nickname) |
E735663
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traffic management scheme nickname |
C24472
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: traffic management scheme nickname Context triple: [Brock (M20 barrier system nickname), instanceOf, traffic management scheme nickname]
-
A.
traffic management scheme
chosen
A traffic management scheme is a coordinated set of policies, controls, and infrastructure measures designed to regulate and optimize the movement of vehicles, pedestrians, and goods within a transportation network.
-
B.
traffic management solution
A traffic management solution is a system that monitors, controls, and optimizes the flow of vehicles and pedestrians across transportation networks to improve safety, reduce congestion, and enhance overall mobility.
-
C.
highway nickname
A highway nickname is an informal, commonly used name or phrase that people use to refer to a specific highway or route instead of its official designation.
-
D.
aviation route nickname
An aviation route nickname is an informal, often memorable name used by pilots, airlines, or enthusiasts to refer to a specific flight path or corridor, typically reflecting its geography, history, or operational characteristics.
-
E.
traffic authority
A traffic authority is an organization or governmental body responsible for planning, regulating, and managing road use, traffic flow, and transportation safety within a specific jurisdiction.
- F. None of above.
Provenance (1 batch)
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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 10:17 a.m.