Triple
T28424057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hisham ibn Urwah |
E720022
|
entity |
| Predicate | narrationsIncludedIn |
P6847
|
FINISHED |
| Object | 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: Sahih al-Bukhari | Statement: [Hisham ibn Urwah, narrationsIncludedIn, Sahih al-Bukhari]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrationsIncludedIn Context triple: [Hisham ibn Urwah, narrationsIncludedIn, Sahih al-Bukhari]
-
A.
containsNarrativeOf
chosen
Indicates that one entity includes or presents the story, account, or narrative content of another entity.
-
B.
narratesWith
Indicates that one entity tells, recounts, or presents a story, event, or information in conjunction with or alongside another entity.
-
C.
narratesPortionsOf
Indicates that one entity recounts, tells, or provides a narrative of specific parts or segments of another entity.
-
D.
narrationRequired
Indicates that an accompanying explanatory or descriptive narrative is required to properly present or understand the related content or event.
-
E.
narratedTo
Indicates that one entity tells or recounts a story, event, or information directly to another entity as the audience.
- 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_69eff6f1c5088190bc24bfbf92f9c017 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 28, 2026, 1:35 a.m.