Triple
T33652884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAS Connect |
E862145
|
entity |
| Predicate | IATACodeSharedWithParent |
P85321
|
FINISHED |
| Object | SK |
—
|
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: SK | Statement: [SAS Connect, IATACodeSharedWithParent, SK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IATACodeSharedWithParent Context triple: [SAS Connect, IATACodeSharedWithParent, SK]
-
A.
associatedWithIATATypeCode
Indicates that one entity is linked to or characterized by a specific IATA type code that classifies its role or function in air transport.
-
B.
hasParentCode
chosen
Indicates that an entity is associated with a parent code from which it is derived or to which it is hierarchically linked.
-
C.
sharesParentsWith
Indicates that two entities have the same parents, making them siblings or otherwise sharing identical parentage.
-
D.
usesIATACodeAtOtherEnd
Indicates that one entity identifies or refers to the other end of a route, connection, or relationship using its IATA airport code.
-
E.
isSharedByFamily
Indicates that something is commonly used, owned, or enjoyed by multiple members of the same family.
- 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:42 a.m.