Triple
T25493439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mafātīḥ al-Ghayb |
E638892
|
entity |
| Predicate | authorNisba |
P164991
|
FINISHED |
| Object | al-Rāzī |
—
|
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: al-Rāzī | Statement: [Mafātīḥ al-Ghayb, authorNisba, al-Rāzī]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorNisba Context triple: [Mafātīḥ al-Ghayb, authorNisba, al-Rāzī]
-
A.
authorType
Indicates the specific role or category of authorship associated with an entity, such as primary author, co-author, or editor.
-
B.
authorOfNamesFor
Indicates that one entity is the creator or originator of the names assigned to another entity or set of entities.
-
C.
authorName
Indicates the name associated with the person or entity that authored a given work or resource.
-
D.
authorTraditionallyAscribedTo
Indicates that authorship of a work is customarily or historically attributed to an entity, even if definitive proof of authorship may be uncertain or disputed.
-
E.
authorFlourished
Indicates that an author was actively producing work or was prominent during a specified time period.
- F. None of above. chosen
Provenance (4 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_69e75dbbd2a88190b70e1e645de14b9a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 21, 2026, 2:39 p.m.