Triple
T20931146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turanians |
E515472
|
entity |
| Predicate | religionInSources |
P39124
|
FINISHED |
| Object | often portrayed as non-Zoroastrian opponents |
—
|
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: often portrayed as non-Zoroastrian opponents | Statement: [Turanians, religionInSources, often portrayed as non-Zoroastrian opponents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religionInSources Context triple: [Turanians, religionInSources, often portrayed as non-Zoroastrian opponents]
-
A.
associatedReligionInTexts
chosen
Indicates that a particular religion is mentioned or linked in written texts in connection with the given entity.
-
B.
religiousTextMentionedIn
Indicates that a religious text is referenced, cited, or discussed within another work or source.
-
C.
originReligionContext
Indicates the religious background or setting from which something or someone originates or is derived.
-
D.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
-
E.
subjectReligion
Indicates that the subject is associated with, practices, or adheres to a particular religion.
- 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_69e0b4fb431c8190b9d40e6a72f0cc87 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f6557e4881909ce932c3f538304a |
completed | April 21, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:49 p.m.