Triple

T33635511
Position Surface form Disambiguated ID Type / Status
Subject People v. Pratt E861679 entity
Predicate hasDefenseClaim P191393 FINISHED
Object Geronimo Pratt was innocent 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: Geronimo Pratt was innocent | Statement: [People v. Pratt, hasDefenseClaim, Geronimo Pratt was innocent]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDefenseClaim
Context triple: [People v. Pratt, hasDefenseClaim, Geronimo Pratt was innocent]
  • A. claimsToDefend
    Indicates that one entity asserts or professes that its actions or stance are intended to protect or uphold another entity or value.
  • B. isDefendedOn
    Indicates that one entity provides protection, justification, or support for another entity in a specific context or situation.
  • C. hasBeenDefendedIn chosen
    Indicates that something (such as a claim, thesis, or position) has been supported or argued for in a particular context, event, or venue.
  • D. hasClaimOn
    Indicates that one entity holds a right, entitlement, or demand over another entity or its resources.
  • E. hasDefenseStrategy
    Indicates that an entity employs or is associated with a particular plan or set of measures designed to protect against threats or attacks.
  • 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_69f34981c54c81909b33c3fa2208a52d completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fef3ceef648190b58027c93d757438 completed May 9, 2026, 8:43 a.m.
PD Predicate disambiguation batch_69fef359da2c819091a034387b08821f completed May 9, 2026, 8:42 a.m.
Created at: May 1, 2026, 1:42 a.m.