Triple

T25935498
Position Surface form Disambiguated ID Type / Status
Subject Rat On! E653540 entity
Predicate isPoliticallyTinged P40887 FINISHED
Object true 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: true | Statement: [Rat On!, isPoliticallyTinged, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isPoliticallyTinged
Context triple: [Rat On!, isPoliticallyTinged, true]
  • A. politicallyIn
    Indicates that one entity is located within, belongs to, or falls under the political jurisdiction or authority of another entity.
  • B. politicallySensitive chosen
    Indicates that an entity, action, or topic is associated with political issues, controversies, or power structures such that it may require special caution, regulation, or discretion.
  • C. hasPoliticalComponent
    Indicates that something includes, involves, or is influenced by political factors, interests, or considerations.
  • D. usedInPoliticalDiscourse
    Indicates that something is employed as a term, concept, or reference within political discussion, debate, or rhetoric.
  • E. politicallySignificant
    Indicates that an entity, event, or action has notable impact on, relevance to, or implications for political processes, power structures, or public policy.
  • 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_69e7ab3fd2f881908837305e4ba98011 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f6041c82b88190a22f9ecee5172883 completed May 2, 2026, 2:03 p.m.
PD Predicate disambiguation batch_69f4a10480748190a2e67bd399fc435d completed May 1, 2026, 12:48 p.m.
Created at: April 22, 2026, 8:39 a.m.