Triple
T5786776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ultra Low Emission Zone |
E128286
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | emissions control zone |
C18841
|
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: emissions control zone Context triple: [Ultra Low Emission Zone, instanceOf, emissions control zone]
-
A.
port emissions reduction initiative
A port emissions reduction initiative is a coordinated program of policies, technologies, and operational changes designed to lower air pollutants and greenhouse gas emissions from maritime, terminal, and landside activities within and around a port.
-
B.
military-controlled zone
A military-controlled zone is a designated geographic area where military authorities exercise primary control over security, movement, and activities, often restricting civilian access and enforcing special regulations.
-
C.
no-take zone
A no-take zone is a designated area, typically in a marine or freshwater environment, where all forms of extractive activities such as fishing, mining, and harvesting are strictly prohibited to protect ecosystems and biodiversity.
-
D.
regulated airspace
Regulated airspace is a defined volume of the atmosphere where aircraft operations are subject to specific rules, restrictions, and oversight by aviation authorities to ensure safety and orderly traffic flow.
-
E.
enclave
An enclave is a distinct, self-contained area or community that is geographically, culturally, or functionally separated from its surrounding environment while remaining embedded within it.
- 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_69c0084450048190bc647b649a05136b |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:51 p.m.