Triple
T26651299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Āyat al-Taṭhīr |
E669064
|
entity |
| Predicate | usedAsProofTextBy |
P89146
|
FINISHED |
| Object | Twelver Shīʿa |
—
|
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: Twelver Shīʿa | Statement: [Āyat al-Taṭhīr, usedAsProofTextBy, Twelver Shīʿa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsProofTextBy Context triple: [Āyat al-Taṭhīr, usedAsProofTextBy, Twelver Shīʿa]
-
A.
usedInProofStyle
Indicates that one entity is employed as a method, technique, or approach within the proof style or strategy of another entity.
-
B.
justificationUsedBy
chosen
Indicates that a particular justification is employed or relied upon by a given entity (such as a person, system, or decision).
-
C.
typicalProofUses
Indicates that a proof characteristically or commonly employs a particular method, technique, or component.
-
D.
usedEvidenceType
Indicates that a particular type or category of evidence was employed or relied upon in a given context or activity.
-
E.
usesProofLanguage
Indicates that one entity employs a specific formal or structured language to express or present a proof related to another entity.
- 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 27, 2026, 2:33 a.m.