Triple
T6000849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samuli Edelmann |
E133590
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Edelmann |
E133590
|
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: Edelmann | Statement: [Samuli Edelmann, familyName, Edelmann]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Edelmann Context triple: [Samuli Edelmann, familyName, Edelmann]
-
A.
Edelmann
chosen
Edelmann is a surname of German origin borne by various individuals across fields such as music, sports, and academia.
-
B.
Hammann
Hammann is a German-origin surname borne by various notable individuals in fields such as aviation, music, and academia.
-
C.
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.
-
D.
Erdman
Erdman is a masculine given name most notably borne by Disney story artist and screenwriter Erdman Penner.
-
E.
Eberl
Eberl is a German-language surname of Austrian and Bavarian origin borne by various notable individuals.
- 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04ee7c0e08190a6e78969448b070a |
completed | March 22, 2026, 8:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c1250c82588190af8102263c1bd242 |
completed | March 23, 2026, 11:33 a.m. |
Created at: March 22, 2026, 4:05 p.m.