Triple
T26225366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian coat of arms |
E655873
|
entity |
| Predicate | 1957UpdateChange |
P60216
|
FINISHED |
| Object | maple leaves changed from green to red |
—
|
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: maple leaves changed from green to red | Statement: [Canadian coat of arms, 1957UpdateChange, maple leaves changed from green to red]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 1957UpdateChange Context triple: [Canadian coat of arms, 1957UpdateChange, maple leaves changed from green to red]
-
A.
changeIn1975
Indicates that a change, transition, or modification in the relationship or state occurred in the year 1975.
-
B.
updatedIn
chosen
Indicates that an entity has undergone a change or modification within a specified time period or version context.
-
C.
statusAfter1956
Indicates the status or condition of an entity as it existed at any time after the year 1956.
-
D.
reformEraChange
Indicates a change or transition that occurs during a period of reform or as part of a reform era.
-
E.
statusAfter1959
Indicates the status or condition of an entity specifically in the period after the year 1959.
- 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d52e1e4819095c8efd797107332 |
completed | May 2, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 8:57 p.m.