Triple
T928484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of Ontario |
E20038
|
entity |
| Predicate | ribbonSymbolism |
P129
|
FINISHED |
| Object | colours of the flag of Ontario |
—
|
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: colours of the flag of Ontario | Statement: [Order of Ontario, ribbonSymbolism, colours of the flag of Ontario]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ribbonSymbolism Context triple: [Order of Ontario, ribbonSymbolism, colours of the flag of Ontario]
-
A.
symbolizes
chosen
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
B.
ribbonHasStripe
Indicates that a ribbon features one or more stripes as part of its pattern or design.
-
C.
protectiveEmblemName
Indicates that a given name is the designated title or label of a protective emblem associated with an entity or context.
-
D.
ribbonAdditionalStripes
Indicates that additional stripes are present on a ribbon beyond its primary or standard design.
-
E.
ribbonDevice
Indicates a relationship where an entity functions as, or is associated with, a ribbon-based device or mechanism.
- 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_69a493af3dc48190adb7263e6e445ea1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b34775ac8190aabbd047a36cec6b |
completed | March 1, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69a4b29876348190a29f4ff9878074a5 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.