Triple
T21380711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hugo von Pohl |
E527345
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | von Pohl |
E802533
|
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: von Pohl | Statement: [Hugo von Pohl, familyName, von Pohl]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: von Pohl Context triple: [Hugo von Pohl, familyName, von Pohl]
-
A.
Pohl
chosen
Pohl is a German surname borne by various notable individuals in fields such as literature, science, and politics.
-
B.
von Kühn
von Kühn is a German noble family name historically associated with figures such as Sophie von Kühn.
-
C.
Pohlmann
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.
-
D.
von Münnich
von Münnich is the noble German family name of Burkhard Christoph von Münnich, an 18th-century military commander and statesman who served in the Russian Empire.
-
E.
von Höpken
Von Höpken is the surname of a notable Swedish noble family most prominently associated with the 18th-century statesman Anders Johan von Höpken.
- 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_69e0b51f363c8190944000ab5523b02b |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b0cdab8c8190a7eebe6e5961ee75 |
completed | April 22, 2026, 11:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a09b42473b08190b0cf48ed71c09de4 |
completed | May 17, 2026, 12:27 p.m. |
Created at: April 16, 2026, 5:11 p.m.