Triple
T36083675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MRZ |
E1043719
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | standard for travel documents |
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: standard for travel documents Context triple: [MRZ, instanceOf, standard for travel documents]
-
A.
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.
-
B.
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.
-
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.
transportation standard
A transportation standard is an agreed-upon set of rules, specifications, and protocols that ensure compatibility, safety, and efficiency across transportation systems, vehicles, and infrastructure.
-
E.
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.
- 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_69f76e3154908190a6f702671c2bea08 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.