Triple

T13521821
Position Surface form Disambiguated ID Type / Status
Subject Oleśnica Piasts E322915 entity
Predicate houseStyle P4631 FINISHED
Object Piast E347554 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: Piast | Statement: [Oleśnica Piasts, houseStyle, Piast]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Piast
Context triple: [Oleśnica Piasts, houseStyle, Piast]
  • A. Piast chosen
    Piast refers to the first historical ruling dynasty of Poland, which governed the Polish lands from the 10th century until the late 14th century.
  • B. Piastów
    Piastów is a small town in east-central Poland that functions as a residential suburb within the Warsaw metropolitan area.
  • C. Bytom Piasts
    The Bytom Piasts were a regional branch of the medieval Polish Piast dynasty that ruled the Duchy of Bytom in Upper Silesia.
  • D. Rawa Piasts
    Rawa Piasts were a regional branch of Poland’s medieval Piast royal family that ruled territories centered around Rawa Mazowiecka.
  • E. Kuyavian Piasts
    The Kuyavian Piasts were a regional branch of Poland’s early medieval Piast royal family that ruled parts of Kuyavia and neighboring lands.
  • 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_69d80766a21881909f21a1b7421d3b8a completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbafa3df0c8190804174695587f0ea completed April 12, 2026, 2:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7549a215c8190a0b18c505d8ca504 completed May 3, 2026, 1:58 p.m.
Created at: April 9, 2026, 9:44 p.m.