Triple
T17052462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maple Leaf |
E413732
|
entity |
| Predicate | flagDesignContext |
P105658
|
FINISHED |
| Object | white square between two red bands |
—
|
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: white square between two red bands | Statement: [Maple Leaf, flagDesignContext, white square between two red bands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flagDesignContext Context triple: [Maple Leaf, flagDesignContext, white square between two red bands]
-
A.
flagDesign
chosen
Indicates the relationship in which one entity is responsible for creating, specifying, or defining the design of a flag associated with another entity.
-
B.
flagDesigner
Indicates that one entity is the person or group responsible for designing the flag associated with another entity.
-
C.
hasDesignContext
Indicates that something is associated with, or defined within, a particular design context or design environment.
-
D.
flagDesignSymbolism
Indicates the symbolic meanings or concepts represented by elements in a flag’s design.
-
E.
flagshipFor
Indicates that one entity serves as the primary or leading representative example for another entity, often embodying its most important qualities or status.
- 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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3daa3324881908d9e445ba1cfe109 |
completed | April 18, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:34 a.m.