Triple

T28923942
Position Surface form Disambiguated ID Type / Status
Subject Vera Claythorne E733592 entity
Predicate presentAtDeathsOf P17673 FINISHED
Object multiple guests on Soldier Island 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: multiple guests on Soldier Island | Statement: [Vera Claythorne, presentAtDeathsOf, multiple guests on Soldier Island]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: presentAtDeathsOf
Context triple: [Vera Claythorne, presentAtDeathsOf, multiple guests on Soldier Island]
  • A. posthumousPresence
    Indicates the continued influence, impact, or perceived presence of an entity after its death or cessation of existence.
  • B. afterDeathOf
    Indicates that one event, state, or condition occurs subsequent to and as a result of the death of a specified entity.
  • C. associatedWithDeathOf chosen
    Indicates a relationship where one entity is connected in some relevant way to the death of another entity, such as by involvement, causation, or contextual association.
  • D. placeOfCessation
    Indicates the location where an entity’s existence, activity, or state comes to an end.
  • E. onceDeceased
    Indicates that an entity was previously dead at some point in time, regardless of its current state.
  • 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_69f05b0a5cc0819094828367ae204b70 completed April 28, 2026, 7 a.m.
NER Named-entity recognition batch_69f74062b9388190b30546cf700a825c completed May 3, 2026, 12:32 p.m.
PD Predicate disambiguation batch_69f73c802b848190b61a416b7488bd96 completed May 3, 2026, 12:16 p.m.
Created at: April 28, 2026, 8:22 a.m.