Triple

T29185793
Position Surface form Disambiguated ID Type / Status
Subject Stephen Byerley E739864 entity
Predicate allegedBackstory P177555 FINISHED
Object injury that required extensive reconstruction 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: injury that required extensive reconstruction | Statement: [Stephen Byerley, allegedBackstory, injury that required extensive reconstruction]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: allegedBackstory
Context triple: [Stephen Byerley, allegedBackstory, injury that required extensive reconstruction]
  • A. allegedFounderInStory
    Indicates that an entity is claimed or reported, within a particular narrative or account, to be the founder of something.
  • B. expandsBackstoryOf
    Indicates that one entity provides additional background details or context that elaborate on the history or origins of another entity.
  • C. hasFictionalBackstory
    Indicates that an entity is associated with an invented or imaginary narrative background rather than a real-world history.
  • D. settingOfCharacterBackstory
    Indicates the place or environment in which a character’s backstory events occur.
  • E. allegedImpostor
    Indicates that one entity is claimed or suspected to be fraudulently posing as another entity.
  • 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_69f07cb74c2c8190ad396487fcb4fde6 completed April 28, 2026, 9:24 a.m.
NER Named-entity recognition batch_69f7009d39508190af7301f824615e88 completed May 3, 2026, 8 a.m.
PD Predicate disambiguation batch_69f6fc53f4f881908dcc698687bbb64d completed May 3, 2026, 7:42 a.m.
PDg Predicate description generation batch_69f6ffb7554881908993d6d2ffbcf8f5 completed May 3, 2026, 7:56 a.m.
Created at: April 28, 2026, 11:59 a.m.