Triple
T6215571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ikhshidid dynasty |
E138977
|
entity |
| Predicate | secondaryReligionOfSubjects |
P26280
|
FINISHED |
| Object | Christianity |
—
|
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: Christianity | Statement: [Ikhshidid dynasty, secondaryReligionOfSubjects, Christianity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryReligionOfSubjects Context triple: [Ikhshidid dynasty, secondaryReligionOfSubjects, Christianity]
-
A.
subjectReligion
Indicates that the subject is associated with, practices, or adheres to a particular religion.
-
B.
laterReligion
Indicates that one religion or religious affiliation chronologically follows or replaces another for the same entity.
-
C.
hasSecondaryReligion
chosen
Indicates that an entity practices, adheres to, or is associated with a secondary religion in addition to its primary religion.
-
D.
otherReligion
Indicates that one entity follows or is associated with a religion that is different from the religion of another entity.
-
E.
associatedReligionText
Indicates that there is a textual work (such as a scripture or religious document) that is specifically associated with, or pertains to, a given 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_69c008aecb0c81909984b48f733ce8ae |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062a0e0488190b71b42386bacf982 |
completed | March 22, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c055fdea3c81908f5d910f0d36234a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:21 p.m.