Triple
T35780988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Armed Forces officers |
E1034434
|
entity |
| Predicate | dutyIncludes |
P137086
|
FINISHED |
| Object | domestic operations |
—
|
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: domestic operations | Statement: [Canadian Armed Forces officers, dutyIncludes, domestic operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dutyIncludes Context triple: [Canadian Armed Forces officers, dutyIncludes, domestic operations]
-
A.
obligationsInclude
Indicates that one obligation set or entity’s responsibilities contain or encompass another specified obligation or subset of duties.
-
B.
dutyLoad
Indicates the amount or extent of responsibility, work, or obligations assigned to an entity.
-
C.
scopeOfDuty
chosen
Indicates the range or extent of responsibilities, tasks, or obligations that an entity is expected or authorized to perform.
-
D.
hasDutiesUnder
Indicates that one party is obligated to perform specific responsibilities or fulfill obligations as defined by another party, agreement, or authority.
-
E.
dutyRecognized
Indicates that an obligation or responsibility has been acknowledged or accepted by the relevant party.
- 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_69f76e14a1e081908eddd57bd6fdb3be |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.