Triple

T36527999
Position Surface form Disambiguated ID Type / Status
Subject Schlacht am Morgarten E900358 entity
Predicate GegnerischerAnführer P1698 FINISHED
Object Leopold I. von Österreich NE NERFINISHED

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: Leopold I. von Österreich | Statement: [Schlacht am Morgarten, GegnerischerAnführer, Leopold I. von Österreich]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: GegnerischerAnführer
Context triple: [Schlacht am Morgarten, GegnerischerAnführer, Leopold I. von Österreich]
  • A. antagonistOf
    Indicates a relationship where one entity actively opposes, conflicts with, or serves as an adversary to another.
  • B. opposingCommander chosen
    Indicates that one entity serves as the commanding officer of a force that is in opposition or conflict with the force commanded by another entity.
  • C. belligerentLeader
    Indicates that an entity serves as a leader or authority figure of a party engaged in a conflict, war, or hostile confrontation.
  • D. besieger
    Indicates that one entity is laying siege to, or conducting a siege against, another entity.
  • E. opponentMonarch
    Indicates that one monarch stands in an opposing or adversarial position to another monarch, typically in conflict or competition.
  • 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_69f76e5eedb88190a393b8c623f71dd7 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7c371931c8190afb1d4dd5157f92c completed May 3, 2026, 9:51 p.m.
PD Predicate disambiguation batch_69f7c1b91fd88190ab85afd626603769 completed May 3, 2026, 9:44 p.m.
Created at: May 3, 2026, 4:11 p.m.