Triple
T32550962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | flag of Uganda |
E831970
|
entity |
| Predicate | emblemBackground |
P174584
|
FINISHED |
| Object | white disc |
—
|
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 disc | Statement: [flag of Uganda, emblemBackground, white disc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emblemBackground Context triple: [flag of Uganda, emblemBackground, white disc]
-
A.
emblemName
Indicates that a specified name is the official or recognized title of an emblem.
-
B.
emblemCaption
Indicates that a text string serves as a caption or descriptive label specifically for an emblem.
-
C.
emblemUsedIn
Indicates that a particular emblem is utilized or displayed within a specific context, setting, or medium.
-
D.
emblemGlyph
Indicates that one entity serves as the specific glyph or graphic symbol used as the emblem for another entity.
-
E.
emblemBrand
Indicates that one entity serves as the emblem, logo, or symbolic mark representing a particular brand.
- F. None of above. chosen
Provenance (4 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c5c70200819080339dcbe1a4088d |
completed | May 3, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 1:02 a.m.