Triple

T25488357
Position Surface form Disambiguated ID Type / Status
Subject Officer John Ryan E638773 entity
Predicate abusesPowerOver P158592 FINISHED
Object Christine Thayer NE NERFINISHED

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: Christine Thayer | Statement: [Officer John Ryan, abusesPowerOver, Christine Thayer]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: abusesPowerOver
Context triple: [Officer John Ryan, abusesPowerOver, Christine Thayer]
  • A. exercisedPowerOver
    Indicates that one entity exerted control, influence, or authority over another entity.
  • B. exercisedPowerWith
    Indicates that one entity actively used or exerted power in conjunction with another entity, implying a shared or coordinated exercise of authority or influence.
  • C. exercisedPowerFrom
    Indicates that one entity exerted authority, control, or influence originating from a particular source, position, or location over another entity or context.
  • D. exercisedPowerAs
    Indicates that one entity actively used or wielded authority, influence, or control in the capacity or role specified by another entity.
  • E. exerciseOfPower
    Indicates the exertion or application of authority, control, or influence by one entity over another or within a given context.
  • 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_69e75dbabeac8190bab30628f8b799d4 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f77dd964819096ec6b2bff5757a6 completed May 2, 2026, 1:09 p.m.
PD Predicate disambiguation batch_69f468421ba08190880eac99135e5970 completed May 1, 2026, 8:45 a.m.
PDg Predicate description generation batch_69f46d361c348190b5fdfd805ecde01b completed May 1, 2026, 9:07 a.m.
Created at: April 21, 2026, 2:33 p.m.