Triple
T10341608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schengen acquis |
E243139
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Schengen rulebook |
C14089
|
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: Schengen rulebook Context triple: [Schengen acquis, instanceOf, Schengen rulebook]
-
A.
European Union convention
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.
treaty implementation rules
Treaty implementation rules are the detailed legal and administrative provisions that translate a treaty’s general obligations into specific, enforceable procedures and standards within a jurisdiction.
-
C.
Europol system
The Europol system is an integrated information and coordination platform that supports European law enforcement agencies in sharing intelligence, analyzing criminal data, and coordinating cross-border investigations.
-
D.
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.
-
E.
EU legal act
chosen
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.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:55 a.m.