Triple

T27214569
Position Surface form Disambiguated ID Type / Status
Subject Kingdom E684100 entity
Predicate perceivesWhisperersAs P56518 FINISHED
Object subversive element 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: subversive element | Statement: [Kingdom, perceivesWhisperersAs, subversive element]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: perceivesWhisperersAs
Context triple: [Kingdom, perceivesWhisperersAs, subversive element]
  • A. hasSupernaturalPerceptionOf
    Indicates that one entity possesses a supernatural or extrasensory awareness, insight, or perception specifically directed toward another entity.
  • B. perceivedByWizardsAs
    Indicates that something is regarded or understood in a particular way specifically from the perspective of wizards.
  • C. revealsBeliefsOf
    Indicates that one entity makes known, exposes, or discloses the beliefs held by another entity.
  • D. hasOppositionalPerception chosen
    Indicates that one entity perceives another entity, concept, or situation as being in opposition, conflict, or contradiction to itself or its interests.
  • E. intendedPerception
    Indicates that one entity is meant or designed to be perceived (e.g., seen, heard, or otherwise sensed) by another entity.
  • 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_69eefad339a08190aeacb2a198f1a39b completed April 27, 2026, 5:57 a.m.
NER Named-entity recognition batch_69f64dbbaefc8190952b8320bf4397d8 completed May 2, 2026, 7:17 p.m.
PD Predicate disambiguation batch_69f64cacd2c08190aed8a1761d0da679 completed May 2, 2026, 7:12 p.m.
Created at: April 27, 2026, 9:40 a.m.