Triple
T33586159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capital Airlines |
E860286
|
entity |
| Predicate | reasonForCeasing |
P13662
|
FINISHED |
| Object | merger with United Air Lines |
—
|
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 with United Air Lines | Statement: [Capital Airlines, reasonForCeasing, merger with United Air Lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForCeasing Context triple: [Capital Airlines, reasonForCeasing, merger with United Air Lines]
-
A.
reasonForDiscontinuation
Indicates that one entity specifies the cause or justification for stopping, ending, or withdrawing another entity, process, or activity.
-
B.
reasonForDisbandment
chosen
Indicates the cause or circumstance that led to a group, organization, or entity being dissolved or disbanded.
-
C.
reasonForLeaving
Indicates the cause, motivation, or circumstance that led an entity to depart or discontinue an association, position, or place.
-
D.
reasonForEndUse
Indicates the justification or purpose explaining why a particular end use or final application occurs or is chosen.
-
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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: May 1, 2026, 1:40 a.m.