Triple

T15548628
Position Surface form Disambiguated ID Type / Status
Subject Michael Huber E370678 entity
Predicate hasFamilyName P18 FINISHED
Object Huber E79860 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: Huber | Statement: [Michael Huber, hasFamilyName, Huber]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Huber
Context triple: [Michael Huber, hasFamilyName, Huber]
  • A. Huber chosen
    Huber is a surname of German origin that is borne by various notable individuals across fields such as science, sports, and the arts.
  • B. Schwarzhuber
    Schwarzhuber is a German surname most notably associated with Johann Schwarzhuber, an SS officer and concentration camp official during World War II.
  • C. Hufstedler
    Hufstedler is the surname of Shirley Hufstedler, a prominent American judge and the first U.S. Secretary of Education.
  • D. Eberl
    Eberl is a German-language surname of Austrian and Bavarian origin borne by various notable individuals.
  • E. Neubauer
    Neubauer is a German surname borne by various notable individuals, including activists, politicians, and academics.
  • 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_69d85cc6cf40819091f4a5facee1ebe6 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04a93121881909d88ca55a39252ac completed April 16, 2026, 2:33 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff455c172c8190833274cb98667e84 completed May 9, 2026, 2:31 p.m.
Created at: April 10, 2026, 4:08 a.m.