Triple

T18168766
Position Surface form Disambiguated ID Type / Status
Subject Petar Bojović E434963 entity
Predicate hasGivenName P17 FINISHED
Object Petar 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: Petar | Statement: [Petar Bojović, hasGivenName, Petar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Petar
Context triple: [Petar Bojović, hasGivenName, Petar]
  • A. Petar chosen
    Petar is a given name commonly used in Slavic countries, equivalent to the English name Peter.
  • B. Pavle
    Pavle is a South Slavic male given name commonly used in countries such as Serbia, Croatia, and Montenegro, equivalent to Paul in English.
  • C. Predrag
    Predrag is the given first name of former Serbian professional basketball player Peja Stojaković.
  • D. Saša
    Saša is a given name commonly used in Slavic countries, often as a diminutive of Aleksandar or Aleksandra.
  • E. Duško
    Duško is the given name of Duško Tadić, a Bosnian Serb who became known as the first person tried by the International Criminal Tribunal for the former Yugoslavia for war crimes committed during the Bosnian War.
  • 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_69d8b90b7a188190b3fc7b8d4a6cd20a completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4df53ef148190a32aad0253547645 completed April 19, 2026, 1:57 p.m.
Created at: April 10, 2026, 10:30 a.m.