Triple
T1918807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yazidism |
E40078
|
entity |
| Predicate | angelRoleOfMelekTaus |
P9987
|
FINISHED |
| Object | chief of the seven holy beings |
—
|
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: chief of the seven holy beings | Statement: [Yazidism, angelRoleOfMelekTaus, chief of the seven holy beings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: angelRoleOfMelekTaus Context triple: [Yazidism, angelRoleOfMelekTaus, chief of the seven holy beings]
-
A.
revelationAngel
Indicates that an angel is the one who delivers or mediates a divine revelation to someone or about something.
-
B.
mythologicalRole
chosen
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
C.
actingRoleType
Indicates the specific type or category of role an entity performs when acting in a particular capacity or function.
-
D.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
E.
eraCharacter
Indicates that a character is associated with, or belongs to, a particular historical or fictional era.
- 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb211eda88190865de7a0522a453d |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafed2ab481908920334e77b1021b |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.