Triple
T28436887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Canadians |
E715290
|
entity |
| Predicate | militaryFunctionContext |
P10341
|
FINISHED |
| Object | Canadian armoured forces tradition |
—
|
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: Canadian armoured forces tradition | Statement: [Royal Canadians, militaryFunctionContext, Canadian armoured forces tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryFunctionContext Context triple: [Royal Canadians, militaryFunctionContext, Canadian armoured forces tradition]
-
A.
militaryFunction
Indicates a relationship where an entity serves a specific role, duty, or operational purpose within a military context.
-
B.
militaryContext
chosen
Indicates that the relationship or action occurs within a military setting, framework, or operational environment.
-
C.
militaryBaseContext
Indicates that the relationship or action occurs within, is associated with, or is influenced by a military base setting or operational environment.
-
D.
functionInWarfare
Indicates the role, purpose, or operational function that something serves within a military or warfare context.
-
E.
fieldOfOperation
Indicates the domain, area, or scope within which an entity operates or carries out its primary activities.
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 28, 2026, 1:43 a.m.