Triple
T18497946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of Ontario |
E451995
|
entity |
| Predicate | usesBritishSymbolism |
P1542
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Flag of Ontario, usesBritishSymbolism, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBritishSymbolism Context triple: [Flag of Ontario, usesBritishSymbolism, true]
-
A.
featuredUnionJackVariant
chosen
Indicates that an entity prominently displays or uses a specific variant of the Union Jack as a key identifying or decorative feature.
-
B.
emblemSymbolism
Indicates that one entity serves as an emblem whose design or features symbolically represent or convey meanings about another entity.
-
C.
BritishSide
Indicates that an entity is aligned with, represents, or belongs to the British side in a conflict, competition, or opposing grouping.
-
D.
symbolismIn
Indicates that one entity functions as a symbol or representation within the context, meaning, or interpretive framework of another entity.
-
E.
emblematicFor
Indicates that something serves as a representative symbol or characteristic example of something else.
- 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e532c15dec8190941e7c7a4cdebb66 |
completed | April 19, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.