Triple
T17715977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AEROSKY |
E442200
|
entity |
| Predicate | relatedToICAOAirlineCode |
P36333
|
FINISHED |
| Object | SKU |
—
|
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: SKU | Statement: [AEROSKY, relatedToICAOAirlineCode, SKU]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToICAOAirlineCode Context triple: [AEROSKY, relatedToICAOAirlineCode, SKU]
-
A.
associatedWithIATAAirlineCode
Indicates that an entity is linked to or identified by a specific IATA airline code.
-
B.
associatedAirlineICAOCode
Indicates the ICAO airline code that is linked to or used by the given entity (such as a flight, route, or service).
-
C.
associatedWithICAOcode
chosen
Indicates a relationship where an entity is linked to, or identified by, a specific ICAO (International Civil Aviation Organization) code.
-
D.
airlineAssociation
Indicates a formal relationship or affiliation between an airline and another entity, such as a partner, alliance, or associated organization.
-
E.
associatedAirlineType
Indicates a relationship where an airline is linked to a specific classification or type (e.g., carrier category or operational class).
- 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47480955481908fa0d3d34aaedd48 |
completed | April 19, 2026, 6:21 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:06 a.m.