Triple
T20817701
| 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 | travel document specification |
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: travel document specification Context triple: [European Union passport design guidelines (color and format) for EEA states, instanceOf, travel document specification]
-
A.
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.
-
B.
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.
-
C.
air transport document
An air transport document is an official record, such as an air waybill or consignment note, that details the terms, conditions, and particulars of goods or passengers being transported by air.
-
D.
identity document
An identity document is an official record issued by an authority that verifies and authenticates a person's identity through personal details and often a photograph or biometric data.
-
E.
identity document technology
Identity document technology encompasses the systems, materials, and processes used to create, secure, verify, and manage official credentials that authenticate an individual’s identity.
- 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.