Triple
T18872597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agreement on the European Economic Area |
E461608
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | EEA Agreement |
C23705
|
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: EEA Agreement Context triple: [Agreement on the European Economic Area, instanceOf, EEA Agreement]
-
A.
European transport agreement
A European transport agreement is a formal, often multilateral, accord between European states that harmonizes rules, standards, and procedures for cross-border transportation of goods and passengers to ensure safety, efficiency, and legal consistency.
-
B.
European Union convention
chosen
A European Union convention is a formal international agreement between EU member states, or between the EU and other parties, that establishes common rules, standards, or cooperation frameworks in specific policy areas.
-
C.
Schengen Area member
A Schengen Area member is a country that participates in the Schengen Agreement, allowing passport-free movement across its borders with other member states while applying common external border and visa policies.
-
D.
EU legal act
An EU legal act is a binding or non-binding instrument adopted by the European Union’s institutions—such as regulations, directives, decisions, recommendations, or opinions—to create, modify, or guide the application of law within the EU legal order.
-
E.
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.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:57 a.m.