Triple

T18350858
Position Surface form Disambiguated ID Type / Status
Subject the Explorer (In the Penal Colony) E439662 entity
Predicate inStoryAction P77863 FINISHED
Object listens to the Officer’s explanation of the apparatus 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: listens to the Officer’s explanation of the apparatus | Statement: [the Explorer (In the Penal Colony), inStoryAction, listens to the Officer’s explanation of the apparatus]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inStoryAction
Context triple: [the Explorer (In the Penal Colony), inStoryAction, listens to the Officer’s explanation of the apparatus]
  • A. narrativeAction chosen
    Indicates an action or event that advances, shapes, or affects the progression of a narrative or story.
  • B. storyBy
    Indicates that one entity is the creator or author of the story associated with another entity.
  • C. storyElement
    Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
  • D. storyEngine
    Indicates that one entity functions as a narrative-generating or plot-controlling mechanism for another entity or set of events.
  • E. storyFunction
    Indicates that one entity serves a particular narrative role or function within the story structure of another 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_69d8b918221c8190a9f7b563d64ac677 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e514f83b648190b473cf611851c666 completed April 19, 2026, 5:46 p.m.
PD Predicate disambiguation batch_69e44fe91bc08190906518e1b120fcf0 completed April 19, 2026, 3:45 a.m.
Created at: April 10, 2026, 10:37 a.m.