Triple
T38292849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hotak Afghan forces |
E1022406
|
entity |
| Predicate | opposedReligionOfEnemy |
P195571
|
FINISHED |
| Object | Twelver Shia Islam |
—
|
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: Twelver Shia Islam | Statement: [Hotak Afghan forces, opposedReligionOfEnemy, Twelver Shia Islam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedReligionOfEnemy Context triple: [Hotak Afghan forces, opposedReligionOfEnemy, Twelver Shia Islam]
-
A.
otherRivalReligion
Indicates that one entity follows or is associated with a religion that is a rival or competing faith to the religion associated with another entity.
-
B.
opposedReligiousGroup
chosen
Indicates that one group is in opposition or conflict with another specifically on religious grounds or beliefs.
-
C.
primaryOpponentsReligion
Indicates the religion or belief system followed by an entity’s main or primary opponent.
-
D.
religiousCounterpart
Indicates that one entity serves as the religious equivalent or analogue of another entity within a different belief system or tradition.
-
E.
opposesDeity
Indicates a relationship where an entity is in conflict with, resists, or acts against a deity.
- 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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: May 3, 2026, 4:30 p.m.