Triple
T1361796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinrich Heine |
E29112
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Heinrich |
E70531
|
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: Heinrich | Statement: [Heinrich Heine, givenName, Heinrich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heinrich Context triple: [Heinrich Heine, givenName, Heinrich]
-
A.
Heinrich
chosen
Heinrich is a masculine given name of German origin that has been borne by numerous historical figures, including nobility, scholars, and political leaders.
-
B.
Hermann
Hermann Minkowski was a German mathematician best known for developing the geometric formulation of special relativity using four-dimensional spacetime.
-
C.
Günther
Günther is a German masculine given name traditionally associated with figures of Germanic origin and culture.
-
D.
Gustav
Gustav is a masculine given name of German origin, borne by several notable historical figures including scientists, artists, and royalty.
-
E.
Wilhelm
Wilhelm is a Germanic given name, equivalent to William, historically borne by numerous European nobles, rulers, and notable figures.
- 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_69a498d77abc8190913bf57e5f51d2c4 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c2b2fb448190bef31375169b4666 |
completed | March 1, 2026, 10:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae0aa0ca0c8190b2d326bf39f750b0 |
completed | March 8, 2026, 11:47 p.m. |
Created at: March 1, 2026, 7:57 p.m.