Triple
T27623053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Taqi |
E696127
|
entity |
| Predicate | religiousRoleAssociation |
P51786
|
FINISHED |
| Object | 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: Imam | Statement: [al-Taqi, religiousRoleAssociation, Imam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousRoleAssociation Context triple: [al-Taqi, religiousRoleAssociation, Imam]
-
A.
associatedReligionRole
chosen
Indicates that one entity holds a specific religious role, office, or function in relation to another entity.
-
B.
religiousHierarchyRole
Indicates that one entity holds a specific position or rank within a religious hierarchy in relation to another entity or institution.
-
C.
ecclesiasticalRole
Indicates that one entity holds or is assigned a specific religious or church-related office, function, or position in relation to another entity.
-
D.
religiousOrientationRole
Indicates a role or position that an entity holds in relation to a particular religious orientation or affiliation.
-
E.
religiousTextRole
Indicates the specific role or function that a religious text has in relation to a person, group, practice, or tradition.
- 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_69ef59092c8881908114ad184248cc46 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: April 27, 2026, 2:16 p.m.