Triple
T38353973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Verden |
E1046272
|
entity |
| Predicate | governmentFormAfterElevation |
P204613
|
FINISHED |
| Object | Prince-bishopric |
—
|
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: Prince-bishopric | Statement: [Diocese of Verden, governmentFormAfterElevation, Prince-bishopric]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentFormAfterElevation Context triple: [Diocese of Verden, governmentFormAfterElevation, Prince-bishopric]
-
A.
governmentFormCreated
Indicates that one entity established or instituted a particular form or system of government for another entity.
-
B.
governmentFormBefore
Indicates that one form of government existed prior to another form of government in a temporal sequence.
-
C.
governmentFormUnder
Indicates that one governmental form or system operates under the authority, framework, or jurisdiction of another governmental form.
-
D.
governmentFormDefined
Indicates that the specific form or structure of governance for an entity has been formally specified or classified.
-
E.
governmentFormEnded
Indicates that a particular form of government for an entity has come to an end or is no longer in effect.
- 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_69f76e3a94fc81908edc175e8d259e80 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:31 p.m.