Triple

T8393258
Position Surface form Disambiguated ID Type / Status
Subject Stefan Nemanja E197992 entity
Predicate monasticName P50298 FINISHED
Object Simeon E380151 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: Simeon | Statement: [Stefan Nemanja, monasticName, Simeon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Simeon
Context triple: [Stefan Nemanja, monasticName, Simeon]
  • A. Simeon
    Simeon is a biblical figure, one of the twelve sons of Jacob and a progenitor of one of the tribes of Israel.
  • B. Simeon chosen
    Simeon is a monastic name referring to Saint Simeon the Myrrh-streaming, a revered Orthodox Christian saint known for the miraculous flow of myrrh from his relics.
  • C. Simeon the God-receiver
    Simeon the God-receiver is a biblical figure in Christian tradition revered as the righteous elder who recognized the infant Jesus as the Messiah during His presentation in the Temple.
  • D. Emmanuel
    Emmanuel is a Belgian prince, a member of the royal family of Belgium and the son of King Philippe and Queen Mathilde.
  • E. Emmanuel
    Emmanuel is a masculine given name of Hebrew origin meaning "God is with us," used in various languages and cultures.
  • 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_69ca82f816bc8190ab321c07d72208c1 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb8184788081909e9857afff629985 completed March 31, 2026, 8:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69cde856a6548190b46e0d8e5cda381b completed April 2, 2026, 3:53 a.m.
Created at: March 30, 2026, 6:03 p.m.