Triple
T30663140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jazz Air |
E780585
|
entity |
| Predicate | allianceThroughPartner |
P158421
|
FINISHED |
| Object | Star Alliance |
—
|
NE NERFINISHED |
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 | Statement: [Jazz Air, allianceThroughPartner, Star Alliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allianceThroughPartner Context triple: [Jazz Air, allianceThroughPartner, Star Alliance]
-
A.
coalitionPartnerWith
Indicates that two entities are formally aligned in a cooperative coalition, sharing goals or actions as partners within that coalition.
-
B.
allianceHubFor
Indicates that one entity serves as a central coordinating hub or focal point for an alliance involving another entity.
-
C.
cooperationPartner
Indicates that two entities are engaged in a collaborative relationship, working together toward shared goals or mutual benefit.
-
D.
allianceProject
Indicates a collaborative project or initiative jointly undertaken by allied entities within an alliance relationship.
-
E.
partnerAffiliation
chosen
Indicates that two entities are formally associated as partners within an organization, project, or collaborative relationship.
- 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_69f224a6d10481909290be1a00fc83b3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:31 p.m.