Triple
T33515630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ansett-ANA |
E858357
|
entity |
| Predicate | mergerNature |
P5868
|
FINISHED |
| Object | merger of private airline with failing competitor |
—
|
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: merger of private airline with failing competitor | Statement: [Ansett-ANA, mergerNature, merger of private airline with failing competitor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergerNature Context triple: [Ansett-ANA, mergerNature, merger of private airline with failing competitor]
-
A.
mergerType
chosen
Indicates the specific kind or category of merger relationship that exists between the involved entities.
-
B.
mergerPartner
Indicates that two entities are involved as counterparties in a merger transaction with each other.
-
C.
mergerResultedIn
Indicates that a merger between entities led to the creation, change, or outcome represented by the related entity or state.
-
D.
mergerResult
Indicates that one or more entities have combined into a single entity, specifying the outcome or resulting entity of the merger.
-
E.
mergerAnnounced
Indicates that an official announcement has been made that two or more entities intend to merge into a single combined entity.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:39 a.m.