Triple
T30818462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ibn Hajar al-Asqalani |
E784850
|
entity |
| Predicate | wroteSectionOn |
P170534
|
FINISHED |
| Object | Kitab al-Iman in Sahih al-Bukhari |
—
|
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: Kitab al-Iman in Sahih al-Bukhari | Statement: [Ibn Hajar al-Asqalani, wroteSectionOn, Kitab al-Iman in Sahih al-Bukhari]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wroteSectionOn Context triple: [Ibn Hajar al-Asqalani, wroteSectionOn, Kitab al-Iman in Sahih al-Bukhari]
-
A.
wroteIn
Indicates that an entity authored or composed something using a particular language, medium, or writing system.
-
B.
areWrittenOn
Indicates that one entity serves as a surface or medium on which another entity is inscribed, recorded, or written.
-
C.
narrativeSectionOf
Indicates that one text segment functions as a narrative section or component within a larger narrative work or document.
-
D.
writtenTo
Indicates that something has been addressed or directed in written form to a particular recipient.
-
E.
laterWrittenIn
Indicates that one text or version was written at a later time than another, establishing a chronological order between the writings.
- 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6906ad50481909a700664e0b70fb0 |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68fb914b88190b0cad83ea9fe9dfc |
completed | May 2, 2026, 11:58 p.m. |
Created at: April 29, 2026, 8:44 p.m.