Triple
T22612070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hans-Karl Freiherr von Esebeck |
E566732
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object |
von Esebeck
Von Esebeck is a German noble family name historically associated with Prussian military officers and aristocracy.
|
E1546203
|
NE FINISHED |
How this triple was built (4 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 Esebeck | Statement: [Hans-Karl Freiherr von Esebeck, familyName, von Esebeck]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: von Esebeck Context triple: [Hans-Karl Freiherr von Esebeck, familyName, von Esebeck]
-
A.
Beckstein
Beckstein is a wine-producing village and district of the town Lauda-Königshofen in the Main-Tauber region of Baden-Württemberg, Germany.
-
B.
von Giesebrecht
von Giesebrecht is a German noble family name historically associated with scholars and public figures such as the historian Friedrich Wilhelm von Giesebrecht.
-
C.
von Soden
Von Soden is a German surname historically associated with notable scholars and public figures, particularly in the fields of theology and Assyriology.
-
D.
Ostriker
Ostriker is a surname most prominently associated with American astrophysicist Jeremiah P. Ostriker and other notable figures in science and the arts.
-
E.
von Reibnitz
Von Reibnitz is a German noble family name historically associated with baronial lineage.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: von Esebeck Triple: [Hans-Karl Freiherr von Esebeck, familyName, von Esebeck]
Generated description
Von Esebeck is a German noble family name historically associated with Prussian military officers and aristocracy.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: von Esebeck Target entity description: Von Esebeck is a German noble family name historically associated with Prussian military officers and aristocracy.
-
A.
Beckstein
Beckstein is a wine-producing village and district of the town Lauda-Königshofen in the Main-Tauber region of Baden-Württemberg, Germany.
-
B.
von Giesebrecht
von Giesebrecht is a German noble family name historically associated with scholars and public figures such as the historian Friedrich Wilhelm von Giesebrecht.
-
C.
von Soden
Von Soden is a German surname historically associated with notable scholars and public figures, particularly in the fields of theology and Assyriology.
-
D.
Ostriker
Ostriker is a surname most prominently associated with American astrophysicist Jeremiah P. Ostriker and other notable figures in science and the arts.
-
E.
von Reibnitz
Von Reibnitz is a German noble family name historically associated with baronial lineage.
- F. None of above. chosen
Provenance (5 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_69e245884860819081046ce07d5872c4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f167eb08c88190bf2380fa8575d2da |
completed | April 29, 2026, 2:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0b4dfb3bbc8190a80293adab818937 |
completed | May 18, 2026, 5:35 p.m. |
| NEDg | Description generation | batch_6a0b4f24dd9c81908f6907c75d4c6da7 |
completed | May 18, 2026, 5:40 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0b4fffea548190b0c3d9cce1c89aa9 |
completed | May 18, 2026, 5:44 p.m. |
Created at: April 17, 2026, 2:57 p.m.