Triple
T25558209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mende people |
E640631
|
entity |
| Predicate | famousArtifactType |
P23131
|
FINISHED |
| Object | Sowei mask |
—
|
NE NERFINISHED |
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: Sowei mask | Statement: [Mende people, famousArtifactType, Sowei mask]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousArtifactType Context triple: [Mende people, famousArtifactType, Sowei mask]
-
A.
notableArtObject
Indicates a relationship where an entity is recognized as an art object of particular significance, prominence, or cultural importance in connection to another entity.
-
B.
notableRelic
Indicates that an entity is a historically or culturally significant relic associated with another entity (such as a place, person, or event).
-
C.
monumentType
Indicates the specific kind or category of monument that an entity is classified as.
-
D.
notableArtifactPursued
Indicates that an entity actively seeks, hunts for, or attempts to obtain a particular notable artifact.
-
E.
hasIconicArtifact
chosen
Indicates that an entity possesses or is associated with a distinctive, emblematic artifact that represents its identity, history, or significance.
- 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_69e75dc1beb08190bac7d76b8d6e7bc4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8cbeda88190a356da7f7ae3437d |
completed | May 2, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 3:44 p.m.