Triple
T31598083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Winnipeg Rifles Cadet Corps |
E806272
|
entity |
| Predicate | usesUniformStyleOf |
P2930
|
FINISHED |
| Object | Canadian Army Cadets |
—
|
NE NERFINISHED |
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 Army Cadets | Statement: [Royal Winnipeg Rifles Cadet Corps, usesUniformStyleOf, Canadian Army Cadets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesUniformStyleOf Context triple: [Royal Winnipeg Rifles Cadet Corps, usesUniformStyleOf, Canadian Army Cadets]
-
A.
uniformStyle
Indicates that the related entities share the same or a consistent style, pattern, or formatting.
-
B.
usesUniform
chosen
Indicates that one entity regularly wears or employs a standardized set of clothing or equipment designated as a uniform.
-
C.
usedStyle
Indicates that one entity employed or applied a particular style, method, or manner associated with another entity.
-
D.
isUniform
Indicates that all elements or parts within a given set, structure, or context share the same characteristics or value.
-
E.
usesAsStyleOf
Indicates that one entity adopts or applies another entity as a stylistic model, method, or manner of expression.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a835ecc48190912306b14b3e2909 |
completed | May 3, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:31 p.m.