Triple
T6792123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rashid Khalifa |
E155957
|
entity |
| Predicate | storyMedium |
P73019
|
FINISHED |
| Object | oral storytelling |
—
|
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: oral storytelling | Statement: [Rashid Khalifa, storyMedium, oral storytelling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyMedium Context triple: [Rashid Khalifa, storyMedium, oral storytelling]
-
A.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
B.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
C.
narrativePassage
Indicates that a segment of text functions as a narrative passage, conveying events, actions, or storytelling rather than exposition, dialogue, or other discourse types.
-
D.
storyFunction
Indicates that one entity serves a particular narrative role or function within the story structure of another entity.
-
E.
storyline
Indicates that one entity serves as the narrative plot or sequence of events associated with another entity.
- 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_69c6881770fc8190972b2906390380f5 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2ae4d1c819089ac6b3abf11a341 |
completed | March 27, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d0979ce0819094678896da4e3169 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1b0d2a48190b249dcc671b9b5e4 |
completed | March 27, 2026, 6:51 p.m. |
Created at: March 27, 2026, 2:15 p.m.