Triple
T29065440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Stack |
E735660
|
entity |
| Predicate | regulatesTrafficTo |
P177444
|
FINISHED |
| Object | Port of Dover |
—
|
NE NERFINISHED |
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: Port of Dover | Statement: [Operation Stack, regulatesTrafficTo, Port of Dover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatesTrafficTo Context triple: [Operation Stack, regulatesTrafficTo, Port of Dover]
-
A.
regulatesTrafficBetween
Indicates that one entity controls, manages, or directs the flow of traffic occurring between two other entities or locations.
-
B.
facilitatesTrafficTowards
chosen
Indicates that one entity enables, promotes, or directs the movement or flow of traffic toward another entity.
-
C.
hasTrafficRegime
Indicates that a specified traffic control or regulatory system applies to a given road, area, or transport context.
-
D.
trafficRestriction
Indicates a limitation or prohibition on the movement or flow of traffic between entities, such as vehicles, routes, or areas.
-
E.
facilitatesTrafficFlowBetween
Indicates that one entity enables, supports, or improves the movement of traffic between two other entities or locations.
- 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_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 28, 2026, 10:17 a.m.