Triple
T16756350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sufriyya |
E407214
|
entity |
| Predicate | viewOnCaliphUthman |
P43906
|
FINISHED |
| Object | critical of late policies of Uthman |
—
|
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: critical of late policies of Uthman | Statement: [Sufriyya, viewOnCaliphUthman, critical of late policies of Uthman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewOnCaliphUthman Context triple: [Sufriyya, viewOnCaliphUthman, critical of late policies of Uthman]
-
A.
viewOnCaliphate
chosen
Indicates a stance, opinion, or perspective that an entity holds regarding the concept, legitimacy, or role of a caliphate.
-
B.
associatedCaliph
Indicates a relationship where an entity is linked or connected to a specific caliph, typically through rule, patronage, affiliation, or historical association.
-
C.
viewOnKalam
Indicates a person's opinion, perspective, or stance regarding Kalam.
-
D.
viewOnIman
Indicates a relationship where one entity holds or expresses a particular opinion, belief, or perspective about Iman.
-
E.
servedCaliph
Indicates that one entity acted in service to, or under the authority of, a caliph.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3abe831ec8190bac05b07db6153c1 |
completed | April 18, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.