Triple
T10412004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICAO airline designator system |
E245413
|
entity |
| Predicate | codeFormatDifferenceFrom |
P130
|
FINISHED |
| Object | IATA airline designator system |
—
|
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 airline designator system | Statement: [ICAO airline designator system, codeFormatDifferenceFrom, IATA airline designator system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeFormatDifferenceFrom Context triple: [ICAO airline designator system, codeFormatDifferenceFrom, IATA airline designator system]
-
A.
hasGrammarDifferenceFrom
Indicates that two linguistic items differ from each other in their grammatical form, structure, or rules of usage.
-
B.
hasLexicalDifferencesWith
Indicates that two linguistic items differ from each other in their word choice or lexical form.
-
C.
differIn
Indicates that two entities are not the same in at least one specified aspect, attribute, or value.
-
D.
codeStandard
Indicates that an entity adheres to, complies with, or is governed by a specified coding or programming standard.
-
E.
format
chosen
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9fc72d081908d81c71133973daf |
completed | April 7, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb6f160819090040644a12395ec |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:10 p.m.