Triple
T6121095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Zimbabwe |
E136483
|
entity |
| Predicate | kuduSymbolize |
P30273
|
FINISHED |
| Object | fauna of Zimbabwe |
—
|
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: fauna of Zimbabwe | Statement: [Coat of arms of Zimbabwe, kuduSymbolize, fauna of Zimbabwe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kuduSymbolize Context triple: [Coat of arms of Zimbabwe, kuduSymbolize, fauna of Zimbabwe]
-
A.
symbolRoot
Indicates a relationship where one symbol serves as the root or base form from which another symbol is derived or structured.
-
B.
symbolReferenced
Indicates that one symbol is mentioned, cited, or otherwise referred to by another symbol.
-
C.
keySymbol
Indicates that one entity serves as the symbolic representation or notation used to denote another entity as a key.
-
D.
appearsWithSymbol
chosen
Indicates that one entity is shown or presented together with a particular symbol in the same visual or contextual setting.
-
E.
symbolForConstant
Indicates that one entity serves as the symbolic representation or notation used to denote a particular constant.
- 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_69c0089f851c81909e5e189a617dcff6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05bf16ad48190958cc46510e02bd3 |
completed | March 22, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69c049f9ab3c81909c8ab6466f6a2935 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:14 p.m.