Triple
T36426343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACD |
E897312
|
entity |
| Predicate | isOfficialReferenceFor |
P83832
|
FINISHED |
| Object | global airline codes |
—
|
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: global airline codes | Statement: [ACD, isOfficialReferenceFor, global airline codes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOfficialReferenceFor Context triple: [ACD, isOfficialReferenceFor, global airline codes]
-
A.
isOfficialSourceFor
chosen
Indicates that one entity is recognized as an authoritative or formally sanctioned provider of information or content about another entity.
-
B.
isOfficial
Indicates that an entity holds formal, authorized, or government-recognized status in a given context.
-
C.
refersToOfficialName
Indicates that one entity is referencing or using the formally recognized, official name of another entity.
-
D.
metaReferenceOf
Indicates that one entity serves as a meta-level reference or description of another entity, rather than being the primary object itself.
-
E.
refersSpecificallyTo
Indicates that one entity makes an explicit, precise reference to another particular entity, distinguishing it from more general or ambiguous references.
- 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_69f76e559b10819099d6655a6e14587c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.