Triple

T7325517
Position Surface form Disambiguated ID Type / Status
Subject Ermin E168862 entity
Predicate relatedTo P37 FINISHED
Object Irmin E195337 NE 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: Irmin | Statement: [Ermin, relatedTo, Irmin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Irmin
Context triple: [Ermin, relatedTo, Irmin]
  • A. Gothardus
    Gothardus is a Latinized form of the name Gotthard, most commonly associated with Saint Gotthard of Hildesheim, an 11th-century German bishop and saint.
  • B. Irminones chosen
    Irminones were a major grouping of early Germanic tribes in central Europe, traditionally associated with the ancestors of later High German–speaking peoples.
  • C. Thankmar
    Thankmar was a 10th-century German nobleman and the eldest son of King Henry the Fowler, whose disputed legitimacy led to his rebellion against his half-brother Otto I.
  • D. Durnan
    Durnan is a surname most notably associated with Bill Durnan, a Hall of Fame Canadian ice hockey goaltender who starred for the Montreal Canadiens in the 1940s.
  • E. Reginherus
    Reginherus is a Germanic personal name, historically related to and cognate with the legendary Norse name Ragnar.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c68a54cacc81908e3b773441f19566 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f04993408190b73fb46d83a632d5 completed March 27, 2026, 9:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7ef0a1200819089fe3e18493d8bee completed March 28, 2026, 3:08 p.m.
Created at: March 27, 2026, 3:03 p.m.