Triple
T18095662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Principality of Quedlinburg |
E433077
|
entity |
| Predicate | hadImperialEstate |
P45988
|
FINISHED |
| Object | bench of prelates |
—
|
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: bench of prelates | Statement: [Principality of Quedlinburg, hadImperialEstate, bench of prelates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadImperialEstate Context triple: [Principality of Quedlinburg, hadImperialEstate, bench of prelates]
-
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.
hadEstate
Indicates that an entity possessed or owned a particular estate or landed property.
-
D.
hasImperialPalace
Indicates that an entity possesses or is the location of an official imperial palace.
-
E.
hadImperialCircle
Indicates that an entity was administratively organized within a specific Imperial Circle of the Holy Roman Empire.
- 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_69d8b907d05c819083cc3bd6021089e6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dd1c56848190be0b8c80b30dba6c |
completed | April 19, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:27 a.m.