Triple

T32914798
Position Surface form Disambiguated ID Type / Status
Subject Act I (Götz von Berlichingen) E841975 entity
Predicate introducesConflict P89395 FINISHED
Object Götz’s conflict with princely 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: Götz’s conflict with princely authority | Statement: [Act I (Götz von Berlichingen), introducesConflict, Götz’s conflict with princely authority]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: introducesConflict
Context triple: [Act I (Götz von Berlichingen), introducesConflict, Götz’s conflict with princely authority]
  • A. conflictIntroduced chosen
    Indicates that a conflict has been newly created or brought into existence between the related entities.
  • B. mentionsConflict
    Indicates that one entity refers to or discusses a dispute, disagreement, or conflict involving another entity.
  • C. reportedConflict
    Indicates that one party has formally reported the existence of a conflict involving another party or situation.
  • D. conflictWith
    Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with each other.
  • E. subConflict
    Indicates that one conflict is a component, phase, or subordinate part of a larger overarching conflict.
  • 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_69f3494779388190a5d3e97f92278be2 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69fd7fdafbe881908a31fcb407af2c34 completed May 8, 2026, 6:16 a.m.
PD Predicate disambiguation batch_69fd7ef0ea908190b5d83f71565bdb1c completed May 8, 2026, 6:13 a.m.
Created at: May 1, 2026, 1:19 a.m.