Triple
T11845214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathay Dragon |
E281756
|
entity |
| Predicate | cessationReason |
P11350
|
FINISHED |
| Object | corporate restructuring by Cathay Pacific |
—
|
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: corporate restructuring by Cathay Pacific | Statement: [Cathay Dragon, cessationReason, corporate restructuring by Cathay Pacific]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cessationReason Context triple: [Cathay Dragon, cessationReason, corporate restructuring by Cathay Pacific]
-
A.
cessation
Indicates the ending or discontinuation of an ongoing action, process, or state.
-
B.
reasonForDiscontinuation
chosen
Indicates that one entity specifies the cause or justification for stopping, ending, or withdrawing another entity, process, or activity.
-
C.
causeOfDiaryCessation
Indicates that one event, condition, or factor is the reason why someone stopped keeping a diary.
-
D.
inactivationReason
Indicates the reason or cause for which an entity, status, or process has been deactivated or made inactive.
-
E.
statedReason
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a65b5ff08190bb58361f6a6acdca |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a254a57481908a1e6ad97919c416 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.