Triple

T14761012
Position Surface form Disambiguated ID Type / Status
Subject Sandomierz Piasts E346859 entity
Predicate titleHeld P7034 FINISHED
Object Duke of Sandomierz E382615 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 Sandomierz | Statement: [Sandomierz Piasts, titleHeld, Duke of Sandomierz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Duke of Sandomierz
Context triple: [Sandomierz Piasts, titleHeld, Duke of Sandomierz]
  • A. Duke of Sandomierz chosen
    The Duke of Sandomierz was a medieval Polish princely title associated with the fragmented Piast-ruled duchy centered on the city of Sandomierz.
  • B. 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.
  • C. 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.
  • D. Duke of Opole
    The Duke of Opole was a noble title associated with the historic Silesian duchy centered on the city of Opole, often held by prominent European aristocrats.
  • E. Duke of Sieradz
    The Duke of Sieradz was a medieval Polish noble title associated with the Piast dynasty and the rule over the Sieradz region in central Poland.
  • 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_69d822e8896c819091169882f9b20486 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dec7f207dc819088a53f717736a121 completed April 14, 2026, 11:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69fef885b07c8190af5e33303af9fbea completed May 9, 2026, 9:04 a.m.
Created at: April 10, 2026, 1:30 a.m.