Triple

T2218261
Position Surface form Disambiguated ID Type / Status
Subject Zemsky Sobor of 1613 E48080 entity
Predicate electorateIncluded P23721 FINISHED
Object boyars LITERAL 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: boyars | Statement: [Zemsky Sobor of 1613, electorateIncluded, boyars]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: electorateIncluded
Context triple: [Zemsky Sobor of 1613, electorateIncluded, boyars]
  • A. electorateIncludes chosen
    Indicates that a particular electorate or voting body contains or encompasses the specified member or group as part of those entitled to participate.
  • B. electorate
    Indicates that an entity functions as the body of people entitled to vote in relation to a particular political unit, office, or decision.
  • C. electorateCategory
    Indicates the classification of an electorate or voter group into a specific category based on defined electoral or demographic criteria.
  • D. electorateState
    Indicates the state or region in which a given electorate (voting district or constituency) is located or to which it belongs.
  • E. hasElectorate
    Indicates that a political representative, office, or governing body is associated with and serves a specific group of voters or electoral district.
  • F. None of above.

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_69a88aa1ee708190862c8c378c41e9eb completed March 4, 2026, 7:40 p.m.
NER Named-entity recognition batch_69abc010bd4c8190ace293b37eac1de5 completed March 7, 2026, 6:05 a.m.
PD Predicate disambiguation batch_69abbdaa26d48190860c33fd464c4845 completed March 7, 2026, 5:54 a.m.
Created at: March 4, 2026, 7:46 p.m.