Triple

T11434470
Position Surface form Disambiguated ID Type / Status
Subject Karl Richter E270969 entity
Predicate givenName P17 FINISHED
Object Karl unclear NED1 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: Karl | Statement: [Karl Richter, givenName, Karl]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Karl
Context triple: [Karl Richter, givenName, Karl]
  • A. Karl
    Karl is the given first name of Charles Proteus Steinmetz, the renowned German-American mathematician and electrical engineer who revolutionized the understanding of alternating current systems.
  • B. Karl
    Karl is a ruthless, long-haired German terrorist and Hans Gruber’s vengeful right-hand man in the action film "Die Hard."
  • C. Karl
    Karl was the given name of Archduke Charles Joseph of Austria, a Habsburg archduke and younger brother of Empress Maria Theresa in the 18th century.
  • D. Karl
    Karl is the given name of Archduke Franz Karl of Austria, a 19th-century Habsburg archduke and father of Emperor Franz Joseph I.
  • E. Karl
    Karl is the given first name of the Marvel Comics sorcerer and Doctor Strange adversary Baron Mordo.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide. chosen

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_69d6aadeef688190874bcecd88b3dd9b completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d806c485f481909dd3d9b0993f3faf completed April 9, 2026, 8:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69ef12a7ea2c81909ac2ce2bbe549ebb completed April 27, 2026, 7:39 a.m.
Created at: April 8, 2026, 9:35 p.m.