Triple
T32810288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchy of Verden |
E839127
|
entity |
| Predicate | wasEcclesiasticalTerritoryUntil |
P87457
|
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, wasEcclesiasticalTerritoryUntil, 1648]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasEcclesiasticalTerritoryUntil Context triple: [Duchy of Verden, wasEcclesiasticalTerritoryUntil, 1648]
-
A.
wasPrinceBishopricUntil
Indicates that an entity functioned as a prince-bishopric up to (and including, or until) a specified point in time.
-
B.
ecclesiasticalTerritory
Indicates that one entity is an ecclesiastical (church-governed) jurisdiction or territory associated with another entity, such as a religious organization or authority.
-
C.
wasEcclesiasticalPrincipality
chosen
Indicates that an entity functioned as a territorial state or principality governed by ecclesiastical (religious) authorities rather than secular rulers.
-
D.
existedAsSeparateDuchyUntil
Indicates that an entity functioned as an independent duchy in its own right up to a specified end date.
-
E.
wasKingdomUntil
Indicates that an entity functioned as a kingdom governing another entity up to a specified end time or event.
- 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_69f3493d35208190b4351b4e85f2fa16 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:15 a.m.