Triple

T37464357
Position Surface form Disambiguated ID Type / Status
Subject Overkill E930996 entity
Predicate requiresInteractionWith P86851 FINISHED
Object enemy minions 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: enemy minions | Statement: [Overkill, requiresInteractionWith, enemy minions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiresInteractionWith
Context triple: [Overkill, requiresInteractionWith, enemy minions]
  • A. specifiesInteractionWith
    Indicates that one entity defines or determines the type, parameters, or nature of interaction it has with another entity.
  • B. requiresControlWith
    Indicates that one entity can only be properly used, operated, or function as intended when another entity exercises control over it.
  • C. requiresAgreementWith
    Indicates that one entity’s action, decision, or validity is contingent upon obtaining consent or formal agreement from another specified entity.
  • D. requiresParticipationOf chosen
    Indicates that one entity’s occurrence, validity, or completion depends on the active involvement or participation of another entity.
  • E. requiresActionFrom
    Indicates that one entity is obligated to perform or initiate some action in response to or as a consequence of another entity 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_69f76ec1a1148190b0a961f188d621b0 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_6a005e8a2f7c819085bfc6f04b866d87 completed May 10, 2026, 10:31 a.m.
PD Predicate disambiguation batch_6a005de82ef08190a015b385d1d3443c completed May 10, 2026, 10:28 a.m.
Created at: May 3, 2026, 4:17 p.m.