Triple
T29065455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Stack |
E735660
|
entity |
| Predicate | trafficDirectionManaged |
P4069
|
FINISHED |
| Object | London-bound carriageway of the M20 |
—
|
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: London-bound carriageway of the M20 | Statement: [Operation Stack, trafficDirectionManaged, London-bound carriageway of the M20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trafficDirectionManaged Context triple: [Operation Stack, trafficDirectionManaged, London-bound carriageway of the M20]
-
A.
trafficDirection
Indicates the direction in which traffic is intended or allowed to move relative to a given reference point or segment.
-
B.
hasTrafficDirection
chosen
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
-
C.
trafficManagementStrategy
Indicates a method or plan used to control, organize, or optimize the flow of traffic within a transportation system.
-
D.
trafficManagementGoal
Indicates a goal or objective related to managing, regulating, or optimizing traffic flow and conditions.
-
E.
routesTrafficThrough
Indicates that network traffic originating from one entity is directed to pass through another entity as an intermediate path or conduit.
- 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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6609a8bfc8190bbf7855ef75416c2 |
completed | May 2, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 10:17 a.m.