Triple
T33512761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Visa Code |
E858291
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Schengen acquis instrument |
C60211
|
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 acquis instrument Context triple: [Visa Code, instanceOf, Schengen acquis instrument]
-
A.
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.
-
B.
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.
-
C.
European Union security and defence policy instrument
A European Union security and defence policy instrument is a formal mechanism, tool, or framework established by the EU to plan, coordinate, and implement collective actions in the fields of security, crisis management, and defence.
-
D.
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.
-
E.
European Union external policy instrument
chosen
A European Union external policy instrument is a formal tool, mechanism, or framework through which the EU pursues its objectives and exerts influence beyond its borders in areas such as diplomacy, trade, security, development, and neighborhood relations.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:39 a.m.