Triple
T718045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fiji Airways |
E14352
|
entity |
| Predicate | previousAllianceStatus |
P14509
|
FINISHED |
| Object | Oneworld connect partner |
—
|
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: Oneworld connect partner | Statement: [Fiji Airways, previousAllianceStatus, Oneworld connect partner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousAllianceStatus Context triple: [Fiji Airways, previousAllianceStatus, Oneworld connect partner]
-
A.
allianceStatus
chosen
Indicates the formal or informal cooperative relationship between entities, such as whether they are allies, neutral, or adversarial.
-
B.
previousAlliancePattern
Indicates a recurring or characteristic way in which alliances were formed, structured, or aligned between entities in the past.
-
C.
changesAllianceOf
Indicates that one entity causes or initiates a change in the alliance or affiliation status of another entity.
-
D.
allianceType
Indicates the specific kind or category of alliance relationship that exists between entities.
-
E.
allianceSupport
Indicates a cooperative relationship where one party provides assistance, resources, or backing to an ally within the context of an alliance.
- 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_69a4934a36e081909e7abef98b898a4e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a577658881909c12951d63d96377 |
completed | March 1, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f38898819089d79bad4f4ff2d2 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.