Triple
T19844699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heino |
E476829
|
entity |
| Predicate | name |
P16
|
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, name, Heino]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heino Context triple: [Heino, name, 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.
Kullervo
Kullervo is a male given name of Finnish origin, notably borne by the politician Kullervo Manner and a tragic hero in the Finnish national epic Kalevala.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658085a148190a305bde0897dfe84 |
completed | April 20, 2026, 4:44 p.m. |
Created at: April 10, 2026, 1:51 p.m.