Triple
T26602846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fusiliers de Sherbrooke |
E667681
|
entity |
| Predicate | hasPeacetimeRole |
P7158
|
FINISHED |
| Object | domestic operations support |
—
|
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 support | Statement: [Fusiliers de Sherbrooke, hasPeacetimeRole, domestic operations support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeacetimeRole Context triple: [Fusiliers de Sherbrooke, hasPeacetimeRole, domestic operations support]
-
A.
peacetimeRole
chosen
Indicates the role, function, or duties an entity holds during periods of peace rather than during wartime or conflict.
-
B.
servedInRole
Indicates that one entity performed duties or held a position within a specified role or office in relation to another entity.
-
C.
hasPostColdWarRole
Indicates that an entity holds or has held a specific role, function, or status in the period following the Cold War.
-
D.
formerMilitaryRole
Indicates that an entity previously held, but no longer holds, a specific military role or position.
-
E.
hasHistoricalRoleAs
Indicates that an entity has served in a specific historical capacity, function, or position during a particular period or context.
- 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_69ee9cfd20348190bb1255d2603efb7a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 27, 2026, 2:13 a.m.