Triple
T3520843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dartford Tunnel |
E74416
|
entity |
| Predicate | hazardousGoodsRestrictions |
P33452
|
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: [Dartford Tunnel, hazardousGoodsRestrictions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hazardousGoodsRestrictions Context triple: [Dartford Tunnel, hazardousGoodsRestrictions, yes]
-
A.
transportRestriction
chosen
Indicates that there are limitations, prohibitions, or special conditions governing the use of a particular mode or means of transportation between entities.
-
B.
restrictedFromUseFor
Indicates that something is prohibited or limited from being used for a specified purpose, context, or application.
-
C.
airTransportableBy
Indicates that something can be transported or carried by air using a specific aircraft or air transport method.
-
D.
notableRestriction
Indicates that there is a significant limitation, constraint, or prohibition that meaningfully affects the entity or its use.
-
E.
customsRegime
Indicates the specific customs treatment or regulatory framework under which goods are imported, exported, or stored.
- 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc4c6ac8819096e9c773f3cccbfb |
completed | March 8, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69adae10689c8190b7dc6d7daa8295b6 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.