Triple

T31538296
Position Surface form Disambiguated ID Type / Status
Subject Audrey Bingham E804669 entity
Predicate conflictDynamic P18893 FINISHED
Object often clashes with Jeff Bingham’s traditional views 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: often clashes with Jeff Bingham’s traditional views | Statement: [Audrey Bingham, conflictDynamic, often clashes with Jeff Bingham’s traditional views]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: conflictDynamic
Context triple: [Audrey Bingham, conflictDynamic, often clashes with Jeff Bingham’s traditional views]
  • A. conflictIn
    Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
  • B. conflictSpecific chosen
    Indicates a specific, concrete instance or type of conflict that exists between the related entities.
  • C. conflictType
    Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
  • D. conflictGoal
    Indicates a relationship where one entity’s goal is incompatible with, obstructs, or opposes another entity’s goal.
  • E. conflictIntroduced
    Indicates that a conflict has been newly created or brought into existence between the related entities.
  • 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_69f348d03ef88190a2b73d7b94b9e02d completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6d74b20a48190900dda1014cc13a8 completed May 3, 2026, 5:04 a.m.
PD Predicate disambiguation batch_69f6d26f27dc8190ae426a3e1573933e completed May 3, 2026, 4:43 a.m.
Created at: April 30, 2026, 10:04 p.m.