Triple
T8043583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grebo masks |
E187492
|
entity |
| Predicate | visualLanguage |
P29429
|
FINISHED |
| Object | geometric abstraction |
—
|
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: geometric abstraction | Statement: [Grebo masks, visualLanguage, geometric abstraction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visualLanguage Context triple: [Grebo masks, visualLanguage, geometric abstraction]
-
A.
visualElements
chosen
Indicates that one entity contains, uses, or is characterized by specific visual components or graphical features associated with another entity.
-
B.
visualCompanion
Indicates that one entity serves as a visual counterpart, partner, or accompanying element to another in a visual context.
-
C.
visualSimplicity
Indicates that something is characterized by a minimal, uncluttered, and easy-to-perceive visual appearance or design.
-
D.
visualizedIn
Indicates that something is represented or depicted within a particular visual medium, view, or visualization.
-
E.
visionOrSign
Indicates a relationship where something is perceived or presented as a vision, sign, or symbolic manifestation, often conveying a message, omen, or divine indication.
- 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_69ca82b00cb48190b59a300f70e97bd7 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f4b5e0c819092949af0f995b850 |
completed | March 31, 2026, 3:28 a.m. |
| PD | Predicate disambiguation | batch_69cb049688208190b32088bd2c5930bc |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:23 p.m.