Triple
T6517617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | early Muslim–Quraysh wars |
E148303
|
entity |
| Predicate | opponentReligion |
P28124
|
FINISHED |
| Object | polytheism of Quraysh |
—
|
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: polytheism of Quraysh | Statement: [early Muslim–Quraysh wars, opponentReligion, polytheism of Quraysh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentReligion Context triple: [early Muslim–Quraysh wars, opponentReligion, polytheism of Quraysh]
-
A.
primaryOpponentsReligion
chosen
Indicates the religion or belief system followed by an entity’s main or primary opponent.
-
B.
otherMajorReligion
Indicates that an entity’s primary religious affiliation is a major religion other than the one currently in focus or being referenced.
-
C.
otherReligion
Indicates that one entity follows or is associated with a religion that is different from the religion of another entity.
-
D.
bearerReligion
Indicates that a bearer (such as a person or entity) adheres to, practices, or is associated with a particular religion.
-
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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ac0ece2081909c14accef90efd7c |
completed | March 27, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69c68ab98c78819081743e614df04e1d |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:44 p.m.