Triple
T7047419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermann Pohlmann |
E163675
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Pohlmann |
E276326
|
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: Pohlmann | Statement: [Hermann Pohlmann, familyName, Pohlmann]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pohlmann Context triple: [Hermann Pohlmann, familyName, Pohlmann]
-
A.
Pohlmann
chosen
Pohlmann was a European officer who became a senior commander in the Maratha army and led its forces against the British at the Battle of Assaye in 1803.
-
B.
Bockelmann
Bockelmann is the birth surname of Austrian-Swiss composer and singer Udo Jürgens.
-
C.
Wesselmann
Wesselmann is a surname most notably associated with Tom Wesselmann, a prominent American Pop Art painter known for his bold, stylized depictions of the nude and everyday consumer objects.
-
D.
Faehlmann
Faehlmann is a surname most notably associated with Friedrich Robert Faehlmann, a prominent 19th-century Estonian writer, physician, and folklorist.
-
E.
Hammann
Hammann is a German-origin surname borne by various notable individuals in fields such as aviation, music, and academia.
- 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_69c6885f598c8190b6b6495c59d8d962 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e24c4004819086002bfe55502374 |
completed | March 27, 2026, 8:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7887e6e50819088c23c9b45861a54 |
completed | March 28, 2026, 7:51 a.m. |
Created at: March 27, 2026, 2:37 p.m.