Triple
T28992059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aerosvit Airlines |
E736050
|
entity |
| Predicate | hadFrequentFlyerProgram |
P13481
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Aerosvit Airlines, hadFrequentFlyerProgram, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadFrequentFlyerProgram Context triple: [Aerosvit Airlines, hadFrequentFlyerProgram, yes]
-
A.
associatedWithFrequentFlyerProgram
chosen
Indicates that an entity has a connection or involvement with a frequent flyer program, such as membership, participation, or affiliation.
-
B.
hasFlownIn
Indicates that an entity has previously traveled by flying in or on another entity (such as an aircraft or similar vehicle).
-
C.
isFlownWith
Indicates that one entity travels by air together with, or using the same flight as, another entity.
-
D.
hasMembershipProgram
Indicates that an entity offers or participates in a structured membership program, typically providing special access, benefits, or services to enrolled members.
-
E.
hasAwardProgram
Indicates that an entity maintains or offers a formal award or recognition program.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65f7dfa3481909a6775b0cef703b3 |
completed | May 2, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:26 a.m.