Triple
T30516546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tawûsê Melek |
E776582
|
entity |
| Predicate | relationToGodInYazidism |
P60881
|
FINISHED |
| Object | servant of God |
—
|
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: servant of God | Statement: [Tawûsê Melek, relationToGodInYazidism, servant of God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToGodInYazidism Context triple: [Tawûsê Melek, relationToGodInYazidism, servant of God]
-
A.
coreStatusInYazidism
Indicates that an entity holds a central, foundational, or defining status within the religious framework of Yazidism.
-
B.
roleInZaydism
Indicates the specific function, position, or status an entity holds within the religious, political, or social structures of Zaydism.
-
C.
relationshipToDeities
chosen
Indicates how an entity is connected or related to one or more deities, such as through worship, lineage, role, or status.
-
D.
relatedNameOfGod
Indicates that one entity is a name, title, or designation that refers to or is associated with God.
-
E.
relationshipToYusuf
Indicates the type or nature of the relationship that one entity has with Yusuf.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0314e613f88190b5dbf89b9c4203c6 |
completed | May 12, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_6a0314699c1c8190b2a80dc4015e7890 |
completed | May 12, 2026, 11:52 a.m. |
Created at: April 29, 2026, 8:16 p.m.