Triple
T27947031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aqidah |
E700908
|
entity |
| Predicate | hasSunniSubtradition |
P191564
|
FINISHED |
| Object | Ashari creed |
—
|
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: Ashari creed | Statement: [Aqidah, hasSunniSubtradition, Ashari creed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSunniSubtradition Context triple: [Aqidah, hasSunniSubtradition, Ashari creed]
-
A.
hasShiaSubtradition
Indicates that an entity follows, belongs to, or is characterized by a specific subtradition within Shia Islam.
-
B.
differsFromSunniIslamIn
Indicates that one belief system, practice, or doctrine is different from Sunni Islam in some specified aspect or respects.
-
C.
otherSunniSchools
Indicates that an entity is associated with Sunni Islamic traditions or schools other than the primary or main one under consideration.
-
D.
consideredShiaSectBy
Indicates that one group or authority regards or classifies another group as belonging to the Shia branch or a Shia sect of Islam.
-
E.
viewInSunniSources
Indicates how something is regarded, interpreted, or evaluated specifically within Sunni Islamic sources or traditions.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
| PDg | Predicate description generation | batch_69fce28a74508190aab36551094e8226 |
completed | May 7, 2026, 7:05 p.m. |
Created at: April 27, 2026, 7:22 p.m.