Triple
T6797451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian Reward |
E156092
|
entity |
| Predicate | airlineAllianceScope |
P73042
|
FINISHED |
| Object | single-airline program |
—
|
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: single-airline program | Statement: [Norwegian Reward, airlineAllianceScope, single-airline program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airlineAllianceScope Context triple: [Norwegian Reward, airlineAllianceScope, single-airline program]
-
A.
airlineAllianceMembership
Indicates that an airline is a member of a specific airline alliance.
-
B.
airlineAllianceStatus
Indicates the formal alliance membership or partnership status that exists between an airline and an airline alliance.
-
C.
servesAirlineAlliance
Indicates that an airline operates flights on behalf of, or under the branding of, a specific airline alliance.
-
D.
airlineAllianceJoinDate
Indicates the date on which an airline became a member of a particular airline alliance.
-
E.
airlineAssociatedBrand
Indicates that a brand is commercially or operationally associated with a particular airline, such as through co-branding, partnership, or subsidiary relationships.
- F. None of above. chosen
Provenance (4 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_69c6881844448190a65822d9b39d7f88 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2ca0c288190a990180fb7cfd08f |
completed | March 27, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69c6d099bf08819089a9f9894d037e74 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d2a8f9188190abbb8c730e7b5edf |
completed | March 27, 2026, 6:55 p.m. |
Created at: March 27, 2026, 2:15 p.m.