Triple
T12032348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IATA Ground Operations Manual |
E286443
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | industry standard manual |
C11832
|
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: industry standard manual Context triple: [IATA Ground Operations Manual, instanceOf, industry standard manual]
-
A.
instructional manual
chosen
An instructional manual is a structured document that provides step-by-step guidance, explanations, and reference information to help users correctly and safely operate, assemble, or understand a product, system, or process.
-
B.
legal manual
A legal manual is a comprehensive reference work that systematically explains laws, regulations, procedures, and best practices to guide legal professionals and informed laypersons in understanding and applying legal principles.
-
C.
IEEE standard
An IEEE standard is a formally documented set of technical specifications and guidelines developed and maintained by the Institute of Electrical and Electronics Engineers to ensure interoperability, safety, and quality across electrical, electronic, and computing technologies.
-
D.
military standard
A military standard is an officially established set of technical, procedural, or quality requirements used by armed forces to ensure compatibility, reliability, and uniformity of equipment, systems, and practices.
-
E.
ICT standard
An ICT standard is an agreed set of technical specifications and guidelines that ensure interoperability, compatibility, security, and quality for information and communication technology products and services.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:47 p.m.