Triple
T16352759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Safety Authority for the Channel Tunnel |
E397099
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | binational regulatory body |
C15820
|
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: binational regulatory body Context triple: [Safety Authority for the Channel Tunnel, instanceOf, binational regulatory body]
-
A.
financial regulatory coordination body
A financial regulatory coordination body is an organization that facilitates collaboration, information-sharing, and policy alignment among multiple financial regulators to promote consistent oversight, reduce systemic risk, and address cross-border or cross-sector regulatory issues.
-
B.
intergovernmental legal body
An intergovernmental legal body is an organization formed by multiple governments to develop, interpret, or oversee the implementation of international legal norms, agreements, and dispute-resolution mechanisms.
-
C.
EU–US body
A formal, institutionalized entity that facilitates structured political, economic, and regulatory dialogue and cooperation between the European Union and the United States.
-
D.
intergovernmental coordination agency
An intergovernmental coordination agency is an organization formed by multiple governments to align policies, share information, and manage joint initiatives across jurisdictions.
-
E.
bilateral commission
chosen
A bilateral commission is a formal joint body established by two parties, typically states or organizations, to negotiate, coordinate, and oversee matters of mutual interest.
- F. None of above.
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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:07 a.m.