Triple
T14465785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Max Beckmann |
E358703
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Beckmann |
E358703
|
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: Beckmann | Statement: [Max Beckmann, familyName, Beckmann]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Beckmann Context triple: [Max Beckmann, familyName, Beckmann]
-
A.
Beckmann
chosen
Beckmann is a German surname most famously associated with the Expressionist painter Max Beckmann.
-
B.
Gomberg
Gomberg is a surname most notably associated with American screenwriter and producer Sy Gomberg.
-
C.
Lindlar
Lindlar is a municipality in western Germany’s North Rhine-Westphalia, known for its rural character and location within the hilly Bergisches Land region.
-
D.
Eschenmoser
Eschenmoser is a Swiss surname most notably associated with Albert Eschenmoser, a prominent organic chemist known for his pioneering work in the synthesis of complex natural products and studies on the origin of life.
-
E.
Gütermann
Gütermann is a German surname most notably associated with the Gütermann family involved in industry and manufacturing, particularly in the production of sewing threads.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91f6d4c08190a12e9a5901ee3508 |
completed | April 14, 2026, 7:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd6499c7188190a79411b471cfa7d4 |
completed | May 8, 2026, 4:20 a.m. |
Created at: April 10, 2026, 1:19 a.m.