Triple
T18873525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ADR |
E461627
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | European 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: European agreement Context triple: [ADR, instanceOf, European agreement]
-
A.
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.
-
B.
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.
-
C.
European Union position
A European Union position is an official, collectively agreed stance or policy adopted by EU institutions or member states on a specific issue, guiding the Union’s actions and negotiations internally and externally.
-
D.
European Council decision
A European Council decision is a binding legal act adopted by the European Council that sets specific rules, measures, or positions for particular situations or addressees within the European Union’s institutional framework.
-
E.
European organisation
A European organisation is an entity based in or primarily serving Europe that coordinates activities, policies, or services across multiple European countries or within a specific European nation.
- 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.