Triple

T13560289
Position Surface form Disambiguated ID Type / Status
Subject Svoboda E323889 entity
Predicate hasVariant P455 FINISHED
Object Swoboda E323889 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: Swoboda | Statement: [Svoboda, hasVariant, Swoboda]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Swoboda
Context triple: [Svoboda, hasVariant, Swoboda]
  • A. Svoboda chosen
    Svoboda is a common Czech surname borne by numerous notable figures, including politicians, artists, and athletes.
  • B. Svobodny
    Svobodny is a town in Russia’s Amur Oblast, known historically as a Trans-Siberian Railway hub and more recently for its proximity to the Vostochny Cosmodrome.
  • C. Alexandrov sloboda
    Alexandrov Sloboda is a historic Russian residence and fortress that served as a key political and religious center, notably functioning as Ivan the Terrible’s main stronghold during his rule.
  • D. Zaslawye
    Zaslawye is a historic town in Belarus known for its medieval origins and location near the capital city, Minsk.
  • E. Площа Свободи
    Площа Свободи — це центральна площа Харкова, одна з найбільших у Європі, відома своїм масштабом та адміністративно-культурним значенням для міста.
  • 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_69d8076830b48190910a902bae5888e2 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbaff5219081909cf60423e79d278f completed April 12, 2026, 2:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69f75dab4974819097880ad4d50f1b34 completed May 3, 2026, 2:37 p.m.
Created at: April 9, 2026, 9:47 p.m.