Triple

T19579287
Position Surface form Disambiguated ID Type / Status
Subject Beránek E489943 entity
Predicate hasPluralForm P5088 FINISHED
Object Beránkovi 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: Beránkovi | Statement: [Beránek, hasPluralForm, Beránkovi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Beránkovi
Context triple: [Beránek, hasPluralForm, Beránkovi]
  • A. Beránek chosen
    Beránek is a Czech surname and word meaning "little lamb," commonly used as a family name in Czech-speaking regions.
  • B. Vamberk
    Vamberk is a Czech town in the Hradec Králové Region renowned for its long tradition of handmade bobbin lace-making.
  • C. Bernolák
    Bernolák is a Slovak surname most notably associated with Anton Bernolák, the 18th-century linguist who codified the first standard form of the Slovak language.
  • D. Beran
    Beran is a Czech surname most notably borne by Rudolf Beran, a prominent Czechoslovak politician and prime minister before and during the early years of World War II.
  • E. Ďurčanský
    Ďurčanský is a Slovak surname most notably associated with Ferdinand Ďurčanský, a 20th-century Slovak politician and lawyer.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8dd9374819098e36349b3211663 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6402763b8819099e535979f094f9d completed April 20, 2026, 3:03 p.m.
Created at: April 10, 2026, 1:42 p.m.