Triple
T2498619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian Airlines |
E52408
|
entity |
| Predicate | airlineAllianceJoinDate |
P40149
|
FINISHED |
| Object | Star Alliance 2000 |
—
|
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: Star Alliance 2000 | Statement: [Austrian Airlines, airlineAllianceJoinDate, Star Alliance 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airlineAllianceJoinDate Context triple: [Austrian Airlines, airlineAllianceJoinDate, Star Alliance 2000]
-
A.
airlineAllianceStatus
Indicates the formal alliance membership or partnership status that exists between an airline and an airline alliance.
-
B.
airlineAllianceMembership
Indicates that an airline is a member of a specific airline alliance.
-
C.
servesAirlineAlliance
Indicates that an airline operates flights on behalf of, or under the branding of, a specific airline alliance.
-
D.
airlineFoundedAs
Indicates that one airline was originally established or created under a particular initial name, structure, or predecessor airline.
-
E.
numberOfMemberAirlines
Indicates the total count of airlines that are members of a specified airline alliance or organization.
- 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_69ab4957b3a88190adf968ae0c1b931c |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd1ae9040819091b3ca5b98659e99 |
completed | March 7, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69abd0bba5348190bb4637d3165cb339 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1aa13a08190a8757c017d8a2478 |
completed | March 7, 2026, 7:20 a.m. |
Created at: March 6, 2026, 9:46 p.m.