Triple

T23128170
Position Surface form Disambiguated ID Type / Status
Subject Heino Ferch E577093 entity
Predicate givenName P17 FINISHED
Object Heino NE NERFINISHED

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: Heino | Statement: [Heino Ferch, givenName, Heino]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Heino
Context triple: [Heino Ferch, givenName, Heino]
  • A. Heino chosen
    Heino is a German schlager singer known for his deep bass voice, trademark dark sunglasses, and popular folk and pop songs since the 1960s.
  • B. Heino
    Heino is a village in the Dutch province of Overijssel, known for its rural character and proximity to the city of Zwolle.
  • C. Eino
    Eino is a Finnish masculine given name most famously borne by the poet Eino Leino.
  • D. Paasio
    Paasio is a Finnish surname most notably associated with Rafael Paasio, a prominent 20th-century Finnish Social Democratic politician and former Prime Minister.
  • E. Hämäläinen
    Hämäläinen is a Finnish surname most notably associated with Olympic and World Championship–winning cross-country skier Marja-Liisa Hämäläinen.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e245f7b0e481909c473ff4e6a54e2c completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18e857b40819081f9df03fff64d48 completed April 29, 2026, 4:52 a.m.
Created at: April 17, 2026, 3:59 p.m.