Triple

T17604613
Position Surface form Disambiguated ID Type / Status
Subject Radomir Putnik E428793 entity
Predicate givenName P17 FINISHED
Object Radomir 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: Radomir | Statement: [Radomir Putnik, givenName, Radomir]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Radomir
Context triple: [Radomir Putnik, givenName, Radomir]
  • A. Radomir chosen
    Radomir is a town in western Bulgaria known for its location in the Pernik Province and its proximity to the Struma River and the capital, Sofia.
  • B. Ilija
    Ilija is a masculine given name of Slavic origin, commonly used in countries such as Bulgaria, Serbia, and North Macedonia.
  • C. Chudomir
    Chudomir was a renowned Bulgarian writer, humorist, and painter known for his satirical short stories and vivid depictions of rural life.
  • D. Branko
    Branko is a masculine given name commonly used in Slavic countries, particularly in the Balkans.
  • E. Miljan
    Miljan is a surname most notably borne by American film actor John Miljan, who appeared in numerous Hollywood productions from the silent era through the 1950s.
  • 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_69d889e1c6148190ba76241e74688f8b completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e46c4b4ee88190827ea28b99ca6f33 completed April 19, 2026, 5:46 a.m.
Created at: April 10, 2026, 5:51 a.m.