Triple
T23719852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CF-104 |
E586109
|
entity |
| Predicate | retiredFromCanadianService |
P132304
|
FINISHED |
| Object | 1986 |
—
|
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: 1986 | Statement: [CF-104, retiredFromCanadianService, 1986]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retiredFromCanadianService Context triple: [CF-104, retiredFromCanadianService, 1986]
-
A.
retiredFromCanadianForces
chosen
Indicates that an individual has ended their service or career in the Canadian Armed Forces.
-
B.
retiredFromCanada
Indicates that an entity has ceased working or ended their professional career while residing in or being associated with Canada.
-
C.
retiredFromFrontlineService
Indicates that an entity has ceased active, primary operational duties and is no longer serving in a frontline role.
-
D.
retiredFromRAAFService
Indicates that an individual has ended or concluded their period of service in the Royal Australian Air Force.
-
E.
retiredFromUSMCFrontlineService
Indicates that an individual has ended their active frontline duty service in the United States Marine Corps.
- 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b77e2dc081908aef7a4c9b188dbd |
completed | April 29, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7 p.m.