Triple
T12888410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-Bishopric of Verden |
E308291
|
entity |
| Predicate | imperialEstate |
P45988
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Prince-Bishopric of Verden, imperialEstate, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imperialEstate Context triple: [Prince-Bishopric of Verden, imperialEstate, Yes]
-
A.
heldImperialEstate
chosen
Indicates that an entity possessed or controlled land or property classified as an imperial estate under a particular imperial authority.
-
B.
establishedAsImperialEstate
Indicates that something has been formally designated or set up as an imperial estate under the authority of an empire.
-
C.
servedAsImperialResidenceFrom
Indicates that an entity functioned as an imperial residence starting from a specified point in time.
-
D.
hasImperialPalace
Indicates that an entity possesses or is the location of an official imperial palace.
-
E.
imperialPolicy
Indicates a policy or set of governing rules imposed or enforced by an imperial authority over its domains or subjects.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97c7f91d08190aac2f6419d3ba992 |
completed | April 10, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69d96fa55b888190ab1612e93c41aec4 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:39 p.m.