Triple
T34769550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarah Little |
E1002323
|
entity |
| Predicate | storyEventsRevolveAround |
P181594
|
FINISHED |
| Object | Sarah Little |
—
|
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: Sarah Little | Statement: [Sarah Little, storyEventsRevolveAround, Sarah Little]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyEventsRevolveAround Context triple: [Sarah Little, storyEventsRevolveAround, Sarah Little]
-
A.
storylineEvent
Indicates that one event occurs as a distinct step or component within a larger narrative or storyline.
-
B.
storySettingEvent
Indicates that an event takes place within, or helps define, the setting or background context of a story.
-
C.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
D.
storyWorld
Indicates the fictional universe or narrative setting within which a story, event, or character exists or takes place.
-
E.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
- 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f77ff804f08190b431a31e6179ace4 |
completed | May 3, 2026, 5:03 p.m. |
Created at: May 3, 2026, 3:59 p.m.