Triple
T12032541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electronic Miscellaneous Document |
E286447
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | air transport document |
C30328
|
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: air transport document Context triple: [Electronic Miscellaneous Document, instanceOf, air transport document]
-
A.
aeronautical document series
An aeronautical document series is an ordered set of related aviation information publications, issued over time in a consistent format, that collectively support the planning, operation, and regulation of air navigation.
-
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 industry standard
A formalized set of rules, guidelines, and technical specifications that ensure safety, interoperability, efficiency, and regulatory compliance across the global air transport industry.
-
D.
maritime transport document
A maritime transport document is an official record, such as a bill of lading or sea waybill, that evidences the contract of carriage of goods by sea, acknowledges receipt of the cargo, and may confer rights to claim delivery.
-
E.
port clearance document
A port clearance document is an official authorization issued by port or maritime authorities confirming that a vessel has met all regulatory, safety, and administrative requirements and is permitted to depart or enter a port.
- F. None of above. chosen
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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:47 p.m.