Triple
T15369359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erich Heckel |
E367500
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Heckel |
E367500
|
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: Heckel | Statement: [Erich Heckel, familyName, Heckel]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heckel Context triple: [Erich Heckel, familyName, Heckel]
-
A.
Heckel
chosen
Heckel is a German surname most notably borne by Expressionist painter and printmaker Erich Heckel, a founding member of the Die Brücke art movement.
-
B.
Schivelbein
Schivelbein is a historic town in northwestern Poland, known today as Świdwin, situated within the Rega River basin.
-
C.
Weisskopf
Weisskopf is a German-language surname borne by various notable individuals in fields such as physics, music, and the arts.
-
D.
Heermann
Heermann is a German surname most notably borne by Johann Heermann, a 17th-century Lutheran hymn writer and poet.
-
E.
Nitzschka
Nitzschka is a village and district of the town of Wurzen in the Free State of Saxony, Germany.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e4b88a881909f9575c02aed287d |
completed | April 16, 2026, 1:41 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff0b50703881909ca71c985bc1c7b5 |
completed | May 9, 2026, 10:24 a.m. |
Created at: April 10, 2026, 3:18 a.m.