Triple
T11999530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-Bishopric of Eichstätt |
E285619
|
entity |
| Predicate | imperialEstateStatus |
P40055
|
FINISHED |
| Object | Imperial immediacy |
—
|
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: Imperial immediacy | Statement: [Prince-Bishopric of Eichstätt, imperialEstateStatus, Imperial immediacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imperialEstateStatus Context triple: [Prince-Bishopric of Eichstätt, imperialEstateStatus, Imperial immediacy]
-
A.
heldImperialEstate
Indicates that an entity possessed or controlled land or property classified as an imperial estate under a particular imperial authority.
-
B.
legalStatusInEmpire
chosen
Indicates the formal legal standing or classification an entity holds within a particular empire’s legal and administrative system.
-
C.
hasEstateType
Indicates that an entity possesses or is associated with a particular category or type of estate.
-
D.
hadEstate
Indicates that an entity possessed or owned a particular estate or landed property.
-
E.
heirOfEstate
Indicates that one entity is legally designated to inherit the estate or property of another entity, typically upon that entity’s death.
- 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903c26d7881909b67a31d04882eb5 |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902b245cc8190af96a9c2bd9c6250 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.