Triple

T15684222
Position Surface form Disambiguated ID Type / Status
Subject Stefan Nemanja E380153 entity
Predicate hasGivenNameForm P15846 FINISHED
Object Stefan E380153 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: Stefan | Statement: [Stefan Nemanja, hasGivenNameForm, Stefan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stefan
Context triple: [Stefan Nemanja, hasGivenNameForm, Stefan]
  • A. Stefan
    Stefan is a masculine given name of Slavic origin, commonly used in many European countries as a variant of Stephen.
  • B. Stefan chosen
    Stefan is the given name of Saint Simeon the Myrrh-streaming, a revered medieval Serbian ruler and Orthodox Christian saint.
  • C. Stefan Reinhardt
    Stefan Reinhardt is a notable individual who shares the Reinhardt surname, recognized as a distinguished bearer of that family name.
  • D. Stefan Rafael Benjamin
    Stefan Rafael Benjamin was the son of the German Jewish philosopher and cultural critic Walter Benjamin.
  • E. Stefan Gregory
    Stefan Gregory is a composer best known for his film score work, including the music for the historical drama "The Dig."
  • 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_69d86d99e860819094b6957cde470f2c completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e04f31b5b881908e46ecd9fc6048ab completed April 16, 2026, 2:53 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff87611d488190857c99e166ac9e8f completed May 9, 2026, 7:13 p.m.
Created at: April 10, 2026, 4:43 a.m.