Triple

T38140857
Position Surface form Disambiguated ID Type / Status
Subject Patrick Hazlewood E952474 entity
Predicate causesInnerConflictIn P20436 FINISHED
Object Tom Burgess 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: Tom Burgess | Statement: [Patrick Hazlewood, causesInnerConflictIn, Tom Burgess]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: causesInnerConflictIn
Context triple: [Patrick Hazlewood, causesInnerConflictIn, Tom Burgess]
  • A. hasCauseOfConflict
    Indicates a relationship where one entity is the source or reason for a conflict involving another entity.
  • B. conflictIn
    Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
  • C. internalConflict chosen
    Indicates a relationship where an entity experiences opposing desires, beliefs, or motives within itself, leading to psychological or emotional tension.
  • D. centralConflictIn
    Indicates that one situation, issue, or opposition serves as the primary source of tension or struggle within another context, such as a story, event, or scenario.
  • E. facedConflictOver
    Indicates that two or more entities experienced opposition, dispute, or tension concerning a particular issue, resource, or situation.
  • 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_69f76f09a7148190a4b91c0bacdc127a completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fd82ed2a4c81908bd7797fbd2e3d08 completed May 8, 2026, 6:30 a.m.
PD Predicate disambiguation batch_69fd814cc10481908e4f8123d35a5d0c completed May 8, 2026, 6:23 a.m.
Created at: May 3, 2026, 4:21 p.m.