Triple
T32625662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-Bishop of Verden |
E834048
|
entity |
| Predicate | wasSovereignOf |
P60298
|
FINISHED |
| Object | Prince-Bishopric of Verden |
—
|
NE NERFINISHED |
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 of Verden | Statement: [Prince-Bishop of Verden, wasSovereignOf, Prince-Bishopric of Verden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasSovereignOf Context triple: [Prince-Bishop of Verden, wasSovereignOf, Prince-Bishopric of Verden]
-
A.
formerSovereign
Indicates that an entity once held sovereign (ruling) authority over another entity but no longer does.
-
B.
fatherIsRulerOf
Indicates that the person who is the father holds the position of ruler or sovereign over the specified entity or domain.
-
C.
wasKingdomUntil
Indicates that an entity functioned as a kingdom governing another entity up to a specified end time or event.
-
D.
governingEmpire
Indicates that one entity serves as the ruling imperial power that controls or governs another entity.
-
E.
rulerOf
chosen
Indicates that one entity holds governing authority or sovereignty over another entity, such as a person ruling a country or territory.
- 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:06 a.m.