Triple
T15379346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erik Heinrichs |
E367757
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object |
Heinrichs
Heinrichs is a German-origin surname borne by various notable individuals, including Finnish general Erik Heinrichs.
|
E1152930
|
NE FINISHED |
How this triple was built (4 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: Heinrichs | Statement: [Erik Heinrichs, familyName, Heinrichs]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heinrichs Context triple: [Erik Heinrichs, familyName, Heinrichs]
-
A.
Heinrich
Heinrich is a masculine given name of German origin that has been borne by numerous historical figures, including nobility, scholars, and political leaders.
-
B.
Heimrich
Heimrich is a Germanic given name of medieval origin, related to names like Heinrich and Henrik and historically borne by various nobles and notable figures in German-speaking regions.
-
C.
Heins
Heins is a variant form of the Dutch surname Heinsius, historically associated with notable scholars and statesmen in the Netherlands.
-
D.
Hein
Hein is a Dutch surname most notably borne by Piet Hein, a renowned 17th-century naval officer and folk hero of the Dutch Republic.
-
E.
Heinsohn
Heinsohn is a surname most prominently associated with Tom Heinsohn, a Hall of Fame Boston Celtics player, coach, and broadcaster.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Heinrichs Triple: [Erik Heinrichs, familyName, Heinrichs]
Generated description
Heinrichs is a German-origin surname borne by various notable individuals, including Finnish general Erik Heinrichs.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Heinrichs Target entity description: Heinrichs is a German-origin surname borne by various notable individuals, including Finnish general Erik Heinrichs.
-
A.
Heinrich
Heinrich is a masculine given name of German origin that has been borne by numerous historical figures, including nobility, scholars, and political leaders.
-
B.
Heimrich
Heimrich is a Germanic given name of medieval origin, related to names like Heinrich and Henrik and historically borne by various nobles and notable figures in German-speaking regions.
-
C.
Heins
Heins is a variant form of the Dutch surname Heinsius, historically associated with notable scholars and statesmen in the Netherlands.
-
D.
Hein
Hein is a Dutch surname most notably borne by Piet Hein, a renowned 17th-century naval officer and folk hero of the Dutch Republic.
-
E.
Heinsohn
Heinsohn is a surname most prominently associated with Tom Heinsohn, a Hall of Fame Boston Celtics player, coach, and broadcaster.
- F. None of above. chosen
Provenance (5 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e6044488190b0499db109f7f821 |
completed | April 16, 2026, 1:41 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff0b5996408190afab2221d38e0027 |
completed | May 9, 2026, 10:24 a.m. |
| NEDg | Description generation | batch_69ff0bf572bc819088ee173d1e0bf5b0 |
completed | May 9, 2026, 10:27 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ff0d5d01308190b1f920042e12b0f3 |
completed | May 9, 2026, 10:33 a.m. |
Created at: April 10, 2026, 3:19 a.m.