Triple
T20817700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Union passport design guidelines (color and format) for EEA states |
E512484
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | passport design standard |
C33106
|
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: passport design standard Context triple: [European Union passport design guidelines (color and format) for EEA states, instanceOf, passport design standard]
-
A.
passport authority
An organization or government agency responsible for issuing, renewing, and regulating passports and related travel documents for citizens.
-
B.
passport union
A passport union is an agreement between two or more jurisdictions that allows citizens to travel, reside, and often work across member states using a shared or mutually recognized passport system with minimal border controls.
-
C.
travel document standard
chosen
A travel document standard is a formalized set of rules and specifications that define the structure, security features, data formats, and interoperability requirements for official documents used to identify and authorize individuals for international travel.
-
D.
smart card standard
A smart card standard is a formal specification that defines the physical, electrical, communication, and data structures required to ensure interoperability and security for smart card technologies across different systems and devices.
-
E.
travel document
A travel document is an official identification, such as a passport or visa, issued by an authority to permit and regulate an individual's international movement across borders.
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:41 p.m.