Triple
T27717554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | hadith of Aisha |
E698862
|
entity |
| Predicate | hasNarratorRoleOf |
P20934
|
FINISHED |
| Object | primary narrator |
—
|
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: primary narrator | Statement: [hadith of Aisha, hasNarratorRoleOf, primary narrator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNarratorRoleOf Context triple: [hadith of Aisha, hasNarratorRoleOf, primary narrator]
-
A.
narratorPlayedBy
Indicates that a given narrator character is portrayed or voiced by a specific performer or actor.
-
B.
hasNarrativeRole
chosen
Indicates that an entity participates in a narrative with a specific functional role (e.g., protagonist, antagonist, narrator) relative to the story.
-
C.
narratorOf
Indicates that one entity serves as the narrator or storytelling voice for another entity, such as a text, story, or media work.
-
D.
narratorRole
Indicates that one entity serves as the narrator of another entity (such as a story, text, or media work), specifying the narrative role or function it performs.
-
E.
hasCoNarrator
Indicates that two or more entities share the role of narrating the same work, event, or story together.
- 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_69ef591012dc8190a6f1ec994f9f7ff7 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 27, 2026, 3:05 p.m.