Triple
T2583550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ibibio people |
E57146
|
entity |
| Predicate | traditionalMaskType |
P40424
|
FINISHED |
| Object | Ekpo mask |
—
|
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: Ekpo mask | Statement: [Ibibio people, traditionalMaskType, Ekpo mask]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalMaskType Context triple: [Ibibio people, traditionalMaskType, Ekpo mask]
-
A.
maskMaterialTradition
Indicates a relationship where a mask is associated with, or originates from, a particular material tradition or customary way of making masks.
-
B.
traditionalCrossType
Indicates that one entity is related to another through a conventional or historically established type of cross or crossing relationship.
-
C.
faceType
Indicates the specific shape or structural category of a face that an entity possesses or is characterized by.
-
D.
costumeType
Indicates the specific kind or category of costume associated with an entity.
-
E.
usesMasksOrDisguises
Indicates that an entity employs masks, costumes, or other forms of disguise to conceal or alter its identity in the context of an action or interaction.
- F. None of above. chosen
Provenance (4 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3cb33a08190a3eae1a95e1b63bf |
completed | March 7, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69abd0cfeae08190aed03866ba071c5c |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd209d934819093600889af9104c3 |
completed | March 7, 2026, 7:21 a.m. |
Created at: March 6, 2026, 9:49 p.m.