Triple
T26277638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BCA |
E660616
|
entity |
| Predicate | operatorFoundedFromMergerOf |
P6637
|
FINISHED |
| Object | Caledonian Airways |
—
|
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: Caledonian Airways | Statement: [BCA, operatorFoundedFromMergerOf, Caledonian Airways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorFoundedFromMergerOf Context triple: [BCA, operatorFoundedFromMergerOf, Caledonian Airways]
-
A.
foundedByMergerOf
chosen
Indicates that an entity was created through the merger or combination of two or more predecessor entities.
-
B.
affiliationBeforeMerger
Indicates that an entity was affiliated with another entity prior to a merger event involving one or both of them.
-
C.
mergerResultedIn
Indicates that a merger between entities led to the creation, change, or outcome represented by the related entity or state.
-
D.
organizationFoundedAs
Indicates that an organization was originally established under a particular name, form, or predecessor entity.
-
E.
affiliationAfterMerger
Indicates that an entity becomes affiliated with another entity as a result of a merger that occurs after a specified point in time.
- 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: April 26, 2026, 9:57 p.m.