Triple

T37808095
Position Surface form Disambiguated ID Type / Status
Subject Copperheads E942558 entity
Predicate usedByOpponentsAs P13821 FINISHED
Object pejorative label 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: pejorative label | Statement: [Copperheads, usedByOpponentsAs, pejorative label]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedByOpponentsAs
Context triple: [Copperheads, usedByOpponentsAs, pejorative label]
  • A. usedAgainst chosen
    Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, another entity.
  • B. allegedByOpponents
    Indicates that a claim or accusation is made by opponents of the subject.
  • C. consideredOpponentsAs
    Indicates that one entity regarded or treated another entity as an opponent or adversary.
  • D. consequenceForOpponents
    Indicates that one party’s actions or status result in negative outcomes, penalties, or repercussions specifically for their opponents.
  • E. sawOpponentsAs
    Indicates perceiving or regarding certain entities as opponents or adversaries.
  • 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_69f76ee8104c8190ab17133ccd8f86e6 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fd974d75e08190af46b1d608769f3b completed May 8, 2026, 7:57 a.m.
PD Predicate disambiguation batch_69fd94ff792c8190bedf4a639d3da809 completed May 8, 2026, 7:47 a.m.
Created at: May 3, 2026, 4:19 p.m.