Triple
T16891298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilhelm von Zweibrücken |
E424178
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | von Zweibrücken |
E235546
|
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 Zweibrücken | Statement: [Wilhelm von Zweibrücken, familyName, von Zweibrücken]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: von Zweibrücken Context triple: [Wilhelm von Zweibrücken, familyName, von Zweibrücken]
-
A.
Zweibrücken-Birkenfeld
Zweibrücken-Birkenfeld was a territorial principality within the Holy Roman Empire ruled by a branch of the Wittelsbach dynasty.
-
B.
Zweibrücken
chosen
Zweibrücken is a historic town in southwestern Germany, known for its former ducal residence, rose garden, and role as the namesake seat of the House of Palatinate-Zweibrücken.
-
C.
von Schlieben
von Schlieben is a German noble family name historically associated with military officers and aristocracy.
-
D.
Erndtebrück
Erndtebrück is a municipality in the Siegen-Wittgenstein district of North Rhine-Westphalia, Germany, known for its rural setting in the Rothaar Mountains.
-
E.
von Teuffenbach
Von Teuffenbach is a German noble surname historically associated with baronial lineage.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3bbc473d4819090cfea374ef5ca49 |
completed | April 18, 2026, 5:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00c2c1eee48190bc906e658d7729a4 |
completed | May 10, 2026, 5:39 p.m. |
Created at: April 10, 2026, 5:29 a.m.