Triple
T9407452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government Service Ensign |
E226621
|
entity |
| Predicate | ensignColorScheme |
P29272
|
FINISHED |
| Object | blue field with Union Flag in the canton |
—
|
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: blue field with Union Flag in the canton | Statement: [Government Service Ensign, ensignColorScheme, blue field with Union Flag in the canton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ensignColorScheme Context triple: [Government Service Ensign, ensignColorScheme, blue field with Union Flag in the canton]
-
A.
hasColourScheme
chosen
Indicates that an entity is associated with a particular set or pattern of colors used in its design or appearance.
-
B.
formerColorScheme
Indicates that an entity previously used a particular color scheme but no longer does so.
-
C.
insigniaColorContext
Indicates the contextual circumstances or conditions under which a particular insignia color is used or holds its specific meaning.
-
D.
capeColor
Indicates the color attribute associated with a cape worn or possessed by an entity.
-
E.
signatureColor
Indicates that an entity has a characteristic or defining color that is uniquely or primarily associated with it.
- 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_69ca843280488190bc65600e843ef9e6 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51c3fc988190ac34cc9e09f8ebfc |
completed | April 1, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:47 p.m.