Triple
T8478360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Brock |
E200451
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road transport contingency plan |
C24473
|
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: road transport contingency plan Context triple: [Operation Brock, instanceOf, road transport contingency plan]
-
A.
regional transport plan
A regional transport plan is a strategic framework that outlines long-term goals, policies, and coordinated investments for transportation systems across a defined geographic region.
-
B.
road transportation corridor
A road transportation corridor is a designated linear area of land that accommodates one or more roadways and associated infrastructure to enable the efficient movement of vehicles, goods, and people between key origins and destinations.
-
C.
transportation route
A transportation route is a defined path or corridor used to move people or goods between locations via one or more modes of transport.
-
D.
road infrastructure
Road infrastructure encompasses the physical structures, systems, and facilities—such as roads, bridges, tunnels, signage, and drainage—designed and built to support safe and efficient vehicular and pedestrian transportation.
-
E.
road traffic agreement
A road traffic agreement is a formal arrangement between parties—such as governments, municipalities, or private entities—that defines rights, responsibilities, and rules for the use, management, and regulation of road traffic within a specified area or network.
- F. None of above. chosen
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_69ca831b17988190a1f3f3413d57b820 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:12 p.m.