Triple
T24567554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evelyn Couch |
E607833
|
entity |
| Predicate | inspiredByStoriesOf |
P44758
|
FINISHED |
| Object | Idgie Threadgoode |
—
|
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: Idgie Threadgoode | Statement: [Evelyn Couch, inspiredByStoriesOf, Idgie Threadgoode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredByStoriesOf Context triple: [Evelyn Couch, inspiredByStoriesOf, Idgie Threadgoode]
-
A.
inspiredByOrRelatedTo
Indicates that one entity draws inspiration from, is influenced by, or is otherwise thematically or conceptually connected to another entity.
-
B.
hasInspired
Indicates that one entity has served as a source of motivation, creativity, or influence leading to ideas, actions, or works in another entity.
-
C.
partlyInspiredBy
Indicates that one entity has been influenced to some extent, but not wholly, by another entity in its creation, development, or form.
-
D.
sourceOfStories
chosen
Indicates that one entity serves as the origin or provider of stories for another entity.
-
E.
inspiredAuthor
Indicates that one entity served as a source of creative or intellectual inspiration for an author entity.
- 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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a92141f88190bcbd7c6aeafc0725 |
completed | April 30, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:28 a.m.