Triple
T9065124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yazidis |
E217225
|
entity |
| Predicate | sacredTextStatus |
P86758
|
FINISHED |
| Object | primarilyOralTradition |
—
|
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: primarilyOralTradition | Statement: [Yazidis, sacredTextStatus, primarilyOralTradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sacredTextStatus Context triple: [Yazidis, sacredTextStatus, primarilyOralTradition]
-
A.
hasSacredText
Indicates that an entity possesses or is associated with a particular sacred or religious text.
-
B.
sacredLanguageStatus
Indicates that a language holds a recognized sacred or liturgical status within a religious or spiritual tradition.
-
C.
scripturalStatus
Indicates the relationship between a text and its recognition or classification as scriptural, canonical, or authoritative within a religious or doctrinal tradition.
-
D.
sacredStatus
Indicates that something holds a revered, holy, or religiously significant status within a particular belief system or tradition.
-
E.
scripturalCanonStatus
Indicates whether and how a text is recognized as part of an authoritative scriptural canon within a given religious or doctrinal tradition.
- 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_69ca83d5a7f48190b16c1e59bd43ede0 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc94bc91d48190acf62afa90eec079 |
completed | April 1, 2026, 3:45 a.m. |
| PD | Predicate disambiguation | batch_69cc65f881248190bfd220bb28a9fb5f |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc668ad3d881908a8a93a6a1d553e4 |
completed | April 1, 2026, 12:27 a.m. |
Created at: March 30, 2026, 7:11 p.m.