Triple
T28244728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-Bishop of Lübeck |
E712131
|
entity |
| Predicate | heldTemporalPowerOver |
P29191
|
FINISHED |
| Object | prince-bishopric estates |
—
|
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 estates | Statement: [Prince-Bishop of Lübeck, heldTemporalPowerOver, prince-bishopric estates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldTemporalPowerOver Context triple: [Prince-Bishop of Lübeck, heldTemporalPowerOver, prince-bishopric estates]
-
A.
heldTemporalPower
chosen
Indicates that an entity exercised governing or authoritative control over another entity or domain during a specific period of time.
-
B.
heldExecutivePowerUntil
Indicates that an entity exercised executive authority or leadership in a role or office up to a specified end date or point in time.
-
C.
heldOf
Indicates that something is possessed, controlled, or kept by a particular entity.
-
D.
heldPowerAlongside
Indicates that two or more entities simultaneously shared and exercised governing or influential authority during the same period.
-
E.
exercisedPowerOver
Indicates that one entity exerted control, influence, or authority over another entity.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 11 p.m.