Triple

T38570075
Position Surface form Disambiguated ID Type / Status
Subject Cleaver E929239 entity
Predicate usedToCreateConflictBetween P75326 FINISHED
Object Christopher Moltisanti 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: Christopher Moltisanti | Statement: [Cleaver, usedToCreateConflictBetween, Christopher Moltisanti]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedToCreateConflictBetween
Context triple: [Cleaver, usedToCreateConflictBetween, Christopher Moltisanti]
  • A. usedByDuringConflict
    Indicates that one entity made practical use of another entity specifically in the context of a particular conflict or war.
  • B. usedInConflictType
    Indicates that something (such as a resource, method, or capability) is employed or applied within a specific type or category of conflict.
  • C. ledToConflict
    Indicates that one event, action, or condition caused or significantly contributed to the emergence or escalation of a conflict between parties.
  • D. conflictWith
    Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with each other.
  • E. triggersConflict chosen
    Indicates that one entity initiates or causes a dispute, clash, or incompatibility to arise with another entity or within a system.
  • 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_69f76ebd2248819083978362d81fa35e completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fcdaa36f90819093f8661969990c7d completed May 7, 2026, 6:32 p.m.
PD Predicate disambiguation batch_69fcd8fefc588190b063d7ea1ec87b07 completed May 7, 2026, 6:25 p.m.
Created at: May 3, 2026, 4:32 p.m.