Triple

T33300205
Position Surface form Disambiguated ID Type / Status
Subject Matt Freehauf E852558 entity
Predicate hasDisabilityInStory P101225 FINISHED
Object physical disability from assault 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: physical disability from assault | Statement: [Matt Freehauf, hasDisabilityInStory, physical disability from assault]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDisabilityInStory
Context triple: [Matt Freehauf, hasDisabilityInStory, physical disability from assault]
  • A. hasDisabilityRepresentation
    Indicates that something includes, portrays, or accounts for the presence and experiences of people with disabilities.
  • B. fictionalDisability
    Indicates that an entity has a disability that exists only in fictional or imaginary contexts, rather than in real-world medical or social classifications.
  • C. portraysCharacterWithDisability chosen
    Indicates that an entity depicts or represents a character who has a disability.
  • D. causeOfDisability
    Indicates that one entity is the reason or source that brings about another entity’s disability.
  • E. disability
    Indicates that an entity has a physical, mental, or sensory impairment that substantially limits one or more major life activities.
  • 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_69f34966ed4c81908dc9dda82d8c7fe3 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69fed09a12648190affcd9bacf7ca275 completed May 9, 2026, 6:13 a.m.
PD Predicate disambiguation batch_69fecf91d6f481908deb60c965c433ed completed May 9, 2026, 6:09 a.m.
Created at: May 1, 2026, 1:33 a.m.