Triple
T13208217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imam Husayn |
E314419
|
entity |
| Predicate | positionInShiaImamate |
P75032
|
FINISHED |
| Object | third Imam |
—
|
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: third Imam | Statement: [Imam Husayn, positionInShiaImamate, third Imam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInShiaImamate Context triple: [Imam Husayn, positionInShiaImamate, third Imam]
-
A.
positionInImamate
chosen
Indicates that one entity holds a specific rank, office, or role within an imamate (a religious-political leadership structure).
-
B.
positionInIslam
Indicates the specific religious role, rank, or status an entity holds within the context of Islam.
-
C.
positionInKutubAlSittah
Indicates the specific placement or ordering of a text or hadith within the canonical six-book collection of Sunni hadith, known as Kutub al-Sittah.
-
D.
recognizesImamateOf
Indicates that one entity acknowledges and accepts the religious or spiritual leadership (imamate) of another entity.
-
E.
roleInShiaPiety
Indicates the specific function, status, or significance an entity holds within Shia religious devotion, practice, or theological understanding.
- 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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98c9cb7ac819095cff8699993c419 |
completed | April 10, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69d98bc938f081909f123bdf1263ff7f |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:17 p.m.