Triple
T17052461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maple Leaf |
E413732
|
entity |
| Predicate | flagDesignElement |
P99574
|
FINISHED |
| Object | central emblem |
—
|
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: central emblem | Statement: [Maple Leaf, flagDesignElement, central emblem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flagDesignElement Context triple: [Maple Leaf, flagDesignElement, central emblem]
-
A.
flagDesign
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.
flagOrInsignia
Indicates that one entity serves as a flag, emblem, or insignia representing another entity.
-
D.
flagDesignSymbolism
chosen
Indicates the symbolic meanings or concepts represented by elements in a flag’s design.
-
E.
symbolDesigned
Indicates that one entity created or planned the design of a symbolic representation (such as a logo, icon, or emblem) for another entity.
- 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.