Triple

T31044379
Position Surface form Disambiguated ID Type / Status
Subject Torwood Excommunication of 1680 E791082 entity
Predicate hasOpposedAuthority P181677 FINISHED
Object Stuart royal authority 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: Stuart royal authority | Statement: [Torwood Excommunication of 1680, hasOpposedAuthority, Stuart royal authority]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOpposedAuthority
Context triple: [Torwood Excommunication of 1680, hasOpposedAuthority, Stuart royal authority]
  • A. hasOpposedActivity
    Indicates that one activity stands in opposition or conflict to another activity.
  • B. hasOppositionalInstitution
    Indicates that one institution stands in an oppositional or adversarial relationship to another institution.
  • C. hasOpposedParty
    Indicates that one party is in an opposing or adversarial position relative to another party, typically within a dispute, conflict, or legal proceeding.
  • D. hasOpposedCondition
    Indicates that one condition stands in direct opposition or contradiction to another condition.
  • E. hasOppositionRoleSince
    Indicates that an entity has held a specific opposition role or position continuously since a given point in time.
  • F. None of above. chosen

Provenance (4 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_69f224ca2fa881908a3ac5fedf207b90 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f7805ce6208190ac6dbd9c97989978 completed May 3, 2026, 5:05 p.m.
PD Predicate disambiguation batch_69f77956ec648190ba4fb7e9d83fd107 completed May 3, 2026, 4:35 p.m.
PDg Predicate description generation batch_69f7805c25dc8190b9977c561ba15975 completed May 3, 2026, 5:05 p.m.
Created at: April 29, 2026, 8:59 p.m.