Triple
T13052488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Uganda |
E327480
|
entity |
| Predicate | spearsSymbolize |
P28265
|
FINISHED |
| Object | readiness to defend independence |
—
|
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: readiness to defend independence | Statement: [Coat of arms of Uganda, spearsSymbolize, readiness to defend independence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spearsSymbolize Context triple: [Coat of arms of Uganda, spearsSymbolize, readiness to defend independence]
-
A.
spearsRepresent
chosen
Indicates that one or more spears serve as a symbol, depiction, or emblem representing a particular entity, concept, or group.
-
B.
symbolizes
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
C.
symbolizedIn
Indicates that one entity serves as a symbol or representation of another entity.
-
D.
towersSymbolize
Indicates that towers serve as symbols representing particular ideas, values, or concepts.
-
E.
symbolElement
Indicates that one entity is a constituent element or component that makes up the other entity, which is treated as a symbol.
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98a9829b48190b23624b6b3df4600 |
completed | April 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69d9803aca4c8190b1015cd159cc47a9 |
completed | April 10, 2026, 10:56 p.m. |
Created at: April 9, 2026, 8:57 p.m.