Triple
T434867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Air Transport Association |
E9789
|
entity |
| Predicate | issuesCodeType |
P2202
|
FINISHED |
| Object | IATA airport code |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: IATA airport code | Statement: [International Air Transport Association, issuesCodeType, IATA airport code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuesCodeType Context triple: [International Air Transport Association, issuesCodeType, IATA airport code]
-
A.
codeType
chosen
Indicates the classification or category assigned to a particular code within a coding or encoding system.
-
B.
relatedCode
Indicates that one code is associated with, linked to, or otherwise contextually connected to another code.
-
C.
code
Indicates that an entity writes, develops, or produces computer software or source code.
-
D.
issues
Indicates that an entity formally produces, releases, or distributes something, such as a document, order, or resource, making it officially available.
-
E.
isOfficialCodeFor
Indicates that one entity serves as the formally recognized or authorized code that designates or identifies another entity.
- F. None of above.
Provenance (3 batches)
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_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ef0b6e0c8190ad6a335ee804829c |
completed | Feb. 28, 2026, 1:35 p.m. |
| PD | Predicate disambiguation | batch_69a2edda55e88190b7c17ba94d7df1ce |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.