Triple

T9260783
Position Surface form Disambiguated ID Type / Status
Subject Emil H. Praeger E222571 entity
Predicate givenName P17 FINISHED
Object Emil E550792 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: Emil | Statement: [Emil H. Praeger, givenName, Emil]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Emil
Context triple: [Emil H. Praeger, givenName, Emil]
  • A. Emil
    Emil is a given name notably borne by Emile Berliner, the German-American inventor best known for developing the gramophone and flat disc record.
  • B. Emil
    Emil is the given name of Carl Gustaf Emil Mannerheim, the renowned Finnish military leader and statesman who served as President of Finland.
  • C. Emil
    Emil is a fictional character from Louisa May Alcott's novel "Jo's Boys," where he appears as one of the next generation of Plumfield children whose adult lives and adventures are followed.
  • D. Emil chosen
    Emil is a masculine given name used in various European languages, often associated with Latin and Germanic origins.
  • E. Oskar
    Oskar is a masculine given name of Germanic origin, commonly used in various European countries.
  • 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_69ca841e4cd481908e738c74e958eaea completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd07175be881908a917573ec9b9081 completed April 1, 2026, 11:52 a.m.
NED1 Entity disambiguation (via context triple) batch_69d09bfb7dfc8190bc337a54083e0dd9 completed April 4, 2026, 5:04 a.m.
Created at: March 30, 2026, 7:32 p.m.