Triple

T13454632
Position Surface form Disambiguated ID Type / Status
Subject Stefan the First-Crowned E311197 entity
Predicate givenName P17 FINISHED
Object Stefan E477080 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 the First-Crowned, givenName, Stefan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stefan
Context triple: [Stefan the First-Crowned, givenName, Stefan]
  • A. Stefan chosen
    Stefan is a masculine given name of Slavic origin, commonly used in many European countries as a variant of Stephen.
  • B. Stefan
    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_69d806a938b8819097ec43a2229fc7f9 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dbaefc52448190b30d7999f44a9765 completed April 12, 2026, 2:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7462522c88190a6a6e2e2292e2414 completed May 3, 2026, 12:57 p.m.
Created at: April 9, 2026, 9:41 p.m.