Triple
T8725694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fran Madison |
E207124
|
entity |
| Predicate | storyTypeContext |
P11858
|
FINISHED |
| Object | supernatural events |
—
|
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: supernatural events | Statement: [Fran Madison, storyTypeContext, supernatural events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyTypeContext Context triple: [Fran Madison, storyTypeContext, supernatural events]
-
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.
storyFunction
Indicates that one entity serves a particular narrative role or function within the story structure of another entity.
-
D.
narrativeType
chosen
Indicates the specific kind or category of narrative (e.g., genre, structural form, or storytelling mode) associated with an entity.
-
E.
storyWorld
Indicates the fictional universe or narrative setting within which a story, event, or character exists or takes place.
- 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d158b0481908249610458f97306 |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:36 p.m.