Triple
T36438472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ally Andrews |
E897657
|
entity |
| Predicate | storyWorldEvent |
P130017
|
FINISHED |
| Object | creatures overrun the world |
—
|
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: creatures overrun the world | Statement: [Ally Andrews, storyWorldEvent, creatures overrun the world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyWorldEvent Context triple: [Ally Andrews, storyWorldEvent, creatures overrun the world]
-
A.
storylineEvent
Indicates that one event occurs as a distinct step or component within a larger narrative or storyline.
-
B.
storyWorld
Indicates the fictional universe or narrative setting within which a story, event, or character exists or takes place.
-
C.
storySettingEvent
chosen
Indicates that an event takes place within, or helps define, the setting or background context of a story.
-
D.
storyEventsRevolveAround
Indicates that the central events or developments in a story primarily concern or are focused on a particular entity or subject.
-
E.
notableStoryEvent
Indicates that an event plays a significant or memorable role within the narrative or storyline associated with the subject.
- 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_69f76e56636481908eda808ab0273401 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:10 p.m.