Triple
T30463495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kayanian cycle |
E775071
|
entity |
| Predicate | hasReligiousFrame |
P202371
|
FINISHED |
| Object | Zoroastrian cosmology |
—
|
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: Zoroastrian cosmology | Statement: [Kayanian cycle, hasReligiousFrame, Zoroastrian cosmology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousFrame Context triple: [Kayanian cycle, hasReligiousFrame, Zoroastrian cosmology]
-
A.
hasReligious
Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
-
B.
hasReligiousSee
Indicates that one entity serves as the ecclesiastical or religious jurisdiction/seat (see) of another entity.
-
C.
hasReligiousType
Indicates that an entity is associated with or classified under a particular religion or religious category.
-
D.
hasReligiousTheme
Indicates that something (such as a work, event, or object) centrally involves or expresses religious ideas, symbols, practices, or narratives.
-
E.
hasReligiousCharacter
Indicates that an entity possesses a religious nature, function, or affiliation, or is characterized by religious aspects or significance.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00776c4ebc8190899005fda34234d5 |
completed | May 10, 2026, 12:17 p.m. |
| PD | Predicate disambiguation | batch_6a0076f8a4c4819093ed577e67aa38f9 |
completed | May 10, 2026, 12:15 p.m. |
| PDg | Predicate description generation | batch_6a00776b69908190a431a48cc5e7dba9 |
completed | May 10, 2026, 12:17 p.m. |
Created at: April 29, 2026, 8:10 p.m.