Triple
T26277629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BCA |
E660616
|
entity |
| Predicate | reasonForEndOfUse |
P11350
|
FINISHED |
| Object | merger of British Caledonian with British Airways |
—
|
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 British Caledonian with British Airways | Statement: [BCA, reasonForEndOfUse, merger of British Caledonian with British Airways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForEndOfUse Context triple: [BCA, reasonForEndOfUse, merger of British Caledonian with British Airways]
-
A.
reasonForUse
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
-
B.
reasonForDiscontinuation
chosen
Indicates that one entity specifies the cause or justification for stopping, ending, or withdrawing another entity, process, or activity.
-
C.
obsoleteReason
Indicates the reason or justification for why something has become obsolete or is no longer in use.
-
D.
reasonForRelease
Indicates the cause, justification, or circumstance that led to an entity being released.
-
E.
reasonForEndOfTerm
Indicates the specific cause or circumstance that led to the termination or conclusion of a term, position, or period of service.
- 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_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 26, 2026, 9:57 p.m.