Triple
T10652786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of the Baobab |
E251011
|
entity |
| Predicate | shapeOfInsignia |
P94451
|
FINISHED |
| Object | representation of a baobab tree |
—
|
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: representation of a baobab tree | Statement: [Order of the Baobab, shapeOfInsignia, representation of a baobab tree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shapeOfInsignia Context triple: [Order of the Baobab, shapeOfInsignia, representation of a baobab tree]
-
A.
emblemSymbolism
Indicates that one entity serves as an emblem whose design or features symbolically represent or convey meanings about another entity.
-
B.
hasHeraldicShieldShape
Indicates that an entity’s heraldic shield is characterized by a specific geometric or stylistic shape.
-
C.
hasLogoShape
chosen
Indicates that an entity’s logo is characterized by or takes the form of a specified geometric or visual shape.
-
D.
coatOfArmsFeatures
Indicates that a coat of arms includes or displays specific symbols, colors, or design elements as part of its heraldic composition.
-
E.
flagOrInsignia
Indicates that one entity serves as a flag, emblem, or insignia representing 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dff78ec88190a4d1863fe87245f6 |
completed | April 8, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69d6dd8753108190b799ffa0c760526e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:06 p.m.