Triple
T14065724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eberhard I, Duke of Württemberg |
E338465
|
entity |
| Predicate | reignAsDukeTo |
P10353
|
FINISHED |
| Object | 1496 |
—
|
LITERAL 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: 1496 | Statement: [Eberhard I, Duke of Württemberg, reignAsDukeTo, 1496]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsDukeTo Context triple: [Eberhard I, Duke of Württemberg, reignAsDukeTo, 1496]
-
A.
succeededAsDuke
Indicates that one individual assumed the title and position of duke previously held by another, directly following them in that role.
-
B.
reignAsDukeOfBavariaTo
Indicates that one entity holds and exercises the title and authority of Duke of Bavaria over another entity (typically a territory or domain).
-
C.
reignAs
chosen
Indicates that an entity holds and exercises ruling authority or sovereignty over a domain or people for a period of time.
-
D.
establishedAsDukes
Indicates that certain individuals or entities were formally created or recognized with the rank and title of dukes.
-
E.
reignAsDauphinTo
Indicates that one person holds and exercises the title and role of Dauphin (heir apparent to the French throne) in relation to a specific monarch or royal line.
- F. None of above.
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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5689c7f48190a47ca94eaa8a9ef9 |
completed | April 14, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.