Triple
T12032587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IATA New Distribution Capability |
E286448
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | XML-based messaging standard |
C3605
|
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: XML-based messaging standard Context triple: [IATA New Distribution Capability, instanceOf, XML-based messaging standard]
-
A.
messaging standard
chosen
A messaging standard is a defined set of rules and formats that enables different systems or applications to exchange messages in a consistent, interoperable, and reliable way.
-
B.
Internet standardization document
An Internet standardization document is an authoritative specification that defines technical protocols, formats, or practices to ensure interoperability and consistent behavior across the global Internet.
-
C.
messaging framework
A messaging framework is a structured system that defines how messages are formatted, transmitted, routed, and processed between distributed components or applications.
-
D.
ASN.1 standard
The ASN.1 standard is a formal notation used to define, encode, transmit, and decode structured data in a platform- and language-independent way, commonly used in telecommunications and cryptographic protocols.
-
E.
XML schema language specification
A formal, machine-readable definition that specifies the structure, constraints, and data types of XML documents to ensure their validity and interoperability.
- 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.