Triple
T27717711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lumʿat al-Iʿtiqad |
E698865
|
entity |
| Predicate | creedScope |
P163109
|
FINISHED |
| Object | summary of core Sunni beliefs |
—
|
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: summary of core Sunni beliefs | Statement: [Lumʿat al-Iʿtiqad, creedScope, summary of core Sunni beliefs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creedScope Context triple: [Lumʿat al-Iʿtiqad, creedScope, summary of core Sunni beliefs]
-
A.
creed
Indicates that an entity holds or is associated with a particular system of religious or ideological belief.
-
B.
recognizesCreed
Indicates that one entity formally accepts or acknowledges the religious or ideological creed of another entity.
-
C.
roleInCreed
Indicates that an entity holds a specific role or function within a particular creed, doctrine, or belief system.
-
D.
supportedCreed
Indicates that one entity endorsed, upheld, or actively promoted a particular belief system, doctrine, or set of principles associated with another entity.
-
E.
positionOnCreed
Indicates a person's stance, alignment, or viewpoint regarding a particular creed, doctrine, or set of beliefs.
- F. None of above. chosen
Provenance (4 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_69ef591012dc8190a6f1ec994f9f7ff7 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63639a84c81909d700a539b458b42 |
completed | May 2, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 27, 2026, 3:05 p.m.