Triple
T16652140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voodoo Medicine Man |
E404631
|
entity |
| Predicate | typicalVisualElements |
P29429
|
FINISHED |
| Object | voodoo symbols |
—
|
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: voodoo symbols | Statement: [Voodoo Medicine Man, typicalVisualElements, voodoo symbols]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalVisualElements Context triple: [Voodoo Medicine Man, typicalVisualElements, voodoo symbols]
-
A.
typicalDesignElement
Indicates that something is a common or characteristic design feature typically found in or associated with another entity.
-
B.
visualElements
chosen
Indicates that one entity contains, uses, or is characterized by specific visual components or graphical features associated with another entity.
-
C.
typicalVisualStyle
Indicates the characteristic or commonly observed visual appearance or aesthetic style associated with an entity.
-
D.
typicalFeatures
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
-
E.
visuallyDefines
Indicates that one entity establishes or clarifies the appearance, form, or visual characteristics of 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37bf7ae7c81908b6807acd8f1669b |
completed | April 18, 2026, 12:41 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.