Triple

T3751796
Position Surface form Disambiguated ID Type / Status
Subject Immanuel Hermann Fichte E81348 entity
Predicate givenName P17 FINISHED
Object Immanuel E19584 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: Immanuel | Statement: [Immanuel Hermann Fichte, givenName, Immanuel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Immanuel
Context triple: [Immanuel Hermann Fichte, givenName, Immanuel]
  • A. Immanuel chosen
    Immanuel is the given name of the influential German philosopher Immanuel Kant, a central figure in modern Western philosophy.
  • B. Emmanuel
    Emmanuel is a Belgian prince, a member of the royal family of Belgium and the son of King Philippe and Queen Mathilde.
  • C. Emmanuel
    Emmanuel is a masculine given name of Hebrew origin meaning "God is with us," used in various languages and cultures.
  • D. Simeon
    Simeon is a biblical figure, one of the twelve sons of Jacob and a progenitor of one of the tribes of Israel.
  • E. Simeon
    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.
  • 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_69ad8b19b7b08190a6188804e99c53e9 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69adcb909bb4819088559f90d718f72f completed March 8, 2026, 7:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4db34aa5c8190ba3f22ee0f1f4208 completed March 14, 2026, 3:51 a.m.
Created at: March 8, 2026, 3:35 p.m.