Triple
T29946537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TAM Linhas Aéreas |
E760645
|
entity |
| Predicate | laterAllianceViaGroup |
P197733
|
FINISHED |
| Object | Oneworld |
—
|
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: Oneworld | Statement: [TAM Linhas Aéreas, laterAllianceViaGroup, Oneworld]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterAllianceViaGroup Context triple: [TAM Linhas Aéreas, laterAllianceViaGroup, Oneworld]
-
A.
alliedGroups
Indicates that two or more groups are formally cooperating or aligned in support of shared goals or interests.
-
B.
involvesAlliance
Indicates that there exists a cooperative or strategic alliance relationship between the referenced entities.
-
C.
alliancesAround
Indicates that alliances are formed or exist in the vicinity or context of a specified entity or focal point.
-
D.
allianceHubFor
Indicates that one entity serves as a central coordinating hub or focal point for an alliance involving another entity.
-
E.
allianceType
Indicates the specific kind or category of alliance relationship that exists between entities.
- 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fea5e828cc8190a9b755a645dc56d2 |
completed | May 9, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69fea36443f08190b2aced9b4a0525fd |
completed | May 9, 2026, 3 a.m. |
| PDg | Predicate description generation | batch_69fea5e75a5481908a04d91ee7255ebb |
completed | May 9, 2026, 3:11 a.m. |
Created at: April 29, 2026, 6:24 p.m.