Triple
T10775224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mihna |
E254180
|
entity |
| Predicate | enforcedDoctrine |
P82058
|
FINISHED |
| Object | created Qur'an |
—
|
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: created Qur'an | Statement: [Mihna, enforcedDoctrine, created Qur'an]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enforcedDoctrine Context triple: [Mihna, enforcedDoctrine, created Qur'an]
-
A.
enforcesDoctrine
chosen
Indicates that one entity compels adherence to, or imposes compliance with, a particular set of doctrines or principles on another entity.
-
B.
reinforcedDoctrine
Indicates that one entity strengthened, supported, or further entrenched a particular doctrine or set of beliefs in another entity or context.
-
C.
confirmedDoctrine
Indicates that an authority has officially validated, endorsed, or ratified a particular doctrine as true or acceptable.
-
D.
followsDoctrine
Indicates that one entity adheres to, complies with, or acts in accordance with a specified doctrine or set of guiding principles.
-
E.
appliedDoctrine
Indicates that a particular doctrine, principle, or rule has been put into practice or used in interpreting or deciding a specific case, situation, or context.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7329cc6c881908f827edff941d456 |
completed | April 9, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69d6f31455648190b5c24690487b1b54 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:16 p.m.