Triple
T14203745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heini |
E352029
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Hein |
E101557
|
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: Hein | Statement: [Heini, hasVariant, Hein]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hein Context triple: [Heini, hasVariant, Hein]
-
A.
Hein
chosen
Hein is a Dutch surname most notably borne by Piet Hein, a renowned 17th-century naval officer and folk hero of the Dutch Republic.
-
B.
Heins
Heins is a variant form of the Dutch surname Heinsius, historically associated with notable scholars and statesmen in the Netherlands.
-
C.
Heini
Heini is a diminutive form of the German given name Heinrich, often used as an affectionate nickname.
-
D.
Hekinan
Hekinan is a coastal industrial city in central Japan known for its manufacturing sector and location along Mikawa Bay in Aichi Prefecture.
-
E.
Helleren
Helleren is a small historic settlement in Norway known for its traditional houses built under a large rock overhang near the Jøssingfjord.
- 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_69d827894ac0819097803e57f3227b23 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61f6d4d481909128084e82e6a58a |
completed | April 14, 2026, 3:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd1951421c81908959634e66857b61 |
completed | May 7, 2026, 10:59 p.m. |
Created at: April 10, 2026, 1:05 a.m.