Triple

T13296955
Position Surface form Disambiguated ID Type / Status
Subject Piasts of Głogów E316708 entity
Predicate hasTitle P38 FINISHED
Object Duke of Głogów E1060889 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: Duke of Głogów | Statement: [Piasts of Głogów, hasTitle, Duke of Głogów]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Duke of Głogów
Context triple: [Piasts of Głogów, hasTitle, Duke of Głogów]
  • A. Duke of Głogów chosen
    The Duke of Głogów was a medieval Silesian noble title held by members of the Piast dynasty who ruled the Głogów region.
  • B. Duke of Inowrocław
    The Duke of Inowrocław was a medieval Polish princely title held by members of the Kuyavian branch of the Piast dynasty who ruled the Inowrocław region.
  • C. Duke of Słupsk
    The Duke of Słupsk was a medieval Pomeranian noble title held by members of the House of Griffins, rulers of the Duchy of Pomerania in what is now northwestern Poland and northeastern Germany.
  • D. Duke of Oleśnica
    The Duke of Oleśnica was a medieval Silesian noble title held by a branch of the Piast dynasty that ruled the Oleśnica (Oels) region.
  • E. Duke of Łęczyca
    The Duke of Łęczyca was a medieval Polish noble title held by members of the Piast dynasty who ruled the Łęczyca region.
  • 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_69d806b40ab4819094adf6c374f4811a completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d990a2f2708190a8f2aa7e7c0b92d2 completed April 11, 2026, 12:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69fbac78104881909ea8d41cfb8d4574 completed May 6, 2026, 9:02 p.m.
Created at: April 9, 2026, 9:28 p.m.