Triple
T19578062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avro Canada CF-105 Arrow |
E489911
|
entity |
| Predicate | cancellationConsequence |
P27792
|
FINISHED |
| Object | mass layoffs at Avro Canada |
—
|
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: mass layoffs at Avro Canada | Statement: [Avro Canada CF-105 Arrow, cancellationConsequence, mass layoffs at Avro Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cancellationConsequence Context triple: [Avro Canada CF-105 Arrow, cancellationConsequence, mass layoffs at Avro Canada]
-
A.
cancellation
Indicates that a previously planned or scheduled event, action, or agreement is being annulled, terminated, or rendered no longer valid.
-
B.
cancellationReason
Indicates the reason or cause for which a previously scheduled or planned action, event, or agreement was canceled.
-
C.
cancels
Indicates that one entity invalidates, nullifies, or stops the effect, operation, or scheduled occurrence of another entity or action.
-
D.
consequenceOfRevocation
chosen
Indicates that something occurs as a direct result of a prior revocation event or decision.
-
E.
canceledBy
Indicates that an action, event, or agreement was annulled or called off by a specific 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e64025d5d081909dbb0c079d366006 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:42 p.m.