Triple
T28880254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Avarayr |
E732395
|
entity |
| Predicate | SasanianSideReligion |
P98884
|
FINISHED |
| Object | Zoroastrianism |
—
|
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: Zoroastrianism | Statement: [Battle of Avarayr, SasanianSideReligion, Zoroastrianism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SasanianSideReligion Context triple: [Battle of Avarayr, SasanianSideReligion, Zoroastrianism]
-
A.
sideSasanian
chosen
Indicates that an entity is aligned with, belongs to, or is on the side of the Sasanian faction or polity in a given context.
-
B.
SasanianUnit
Indicates a relationship where an entity functions as a military or administrative unit within the Sasanian Empire.
-
C.
inZoroastrianism
Indicates that the subject is situated, recognized, or holds a role within the religious context, beliefs, or practices of Zoroastrianism.
-
D.
religiousSide
Indicates that one entity is aligned with, belongs to, or represents a particular religious faction, denomination, or side in a religious context.
-
E.
otherMajorReligion
Indicates that an entity’s primary religious affiliation is a major religion other than the one currently in focus or being referenced.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 7:43 a.m.