Triple
T18965571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Ensign of Canada |
E464028
|
entity |
| Predicate | coatOfArmsVersion |
P133975
|
FINISHED |
| Object | 1868 arms of the Canadian provinces |
—
|
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: 1868 arms of the Canadian provinces | Statement: [Red Ensign of Canada, coatOfArmsVersion, 1868 arms of the Canadian provinces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coatOfArmsVersion Context triple: [Red Ensign of Canada, coatOfArmsVersion, 1868 arms of the Canadian provinces]
-
A.
coatOfArms
Indicates that one entity serves as the heraldic emblem or coat of arms representing another entity.
-
B.
coatOfArmsCaption
Indicates the descriptive text that explains or labels the depicted coat of arms.
-
C.
coatOfArmsType
Indicates the specific kind or category of coat of arms associated with an entity.
-
D.
replacedOnCoatOfArmsBy
Indicates that one element or symbol on a coat of arms has been superseded and taken the place of by another element or symbol.
-
E.
usesCoatOfArmsVariant
Indicates that an entity employs an alternative or modified version of a standard coat of arms rather than the primary or original design.
- F. None of above. chosen
Provenance (4 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d5d663948190b496fbd2e69c7f43 |
completed | April 20, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, noon