Triple
T32810262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchy of Verden |
E839127
|
entity |
| Predicate | establishedAsSecularDuchy |
P186483
|
FINISHED |
| Object | 1648 |
—
|
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: 1648 | Statement: [Duchy of Verden, establishedAsSecularDuchy, 1648]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsSecularDuchy Context triple: [Duchy of Verden, establishedAsSecularDuchy, 1648]
-
A.
existedAsSeparateDuchyUntil
Indicates that an entity functioned as an independent duchy in its own right up to a specified end date.
-
B.
createdAsDuchy
Indicates that an entity was established or formed with the political status or rank of a duchy.
-
C.
endedAsPrincipality
Indicates that an entity’s existence or historical development concluded with it having the political status of a principality.
-
D.
establishedAsPrinceBishopric
Indicates that an entity was formally created or designated as a prince-bishopric, combining both secular princely authority and ecclesiastical bishopric status.
-
E.
elevatedToArchduchy
Indicates that an entity’s status or rank has been raised to that of an archduchy.
- F. None of above. chosen
Provenance (4 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_69f3493d35208190b4351b4e85f2fa16 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 1, 2026, 1:15 a.m.