Triple
T19196177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franz von Waldeck |
E469973
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | von Waldeck |
—
|
NE NERFINISHED |
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 Waldeck | Statement: [Franz von Waldeck, familyName, von Waldeck]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: von Waldeck Context triple: [Franz von Waldeck, familyName, von Waldeck]
-
A.
Graf zu Waldeck
chosen
Graf zu Waldeck is a noble title historically borne by members of the German princely House of Waldeck.
-
B.
von Falkenhausen
Von Falkenhausen is a German noble family name historically associated with military and administrative figures in Prussia and the German Empire.
-
C.
Waldeck-Frankenberg
Waldeck-Frankenberg is a rural district in northern Hesse, Germany, known for its scenic landscapes, forests, and small historic towns.
-
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 Schlieben
von Schlieben is a German noble family name historically associated with military officers and aristocracy.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8dd0ad9088190a173b32657ae2e7a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f8a5dabc81908fffad811f177b03 |
completed | April 20, 2026, 9:57 a.m. |
Created at: April 10, 2026, 12:07 p.m.