Triple
T14715130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medieval Prince-Bishopric of Magdeburg |
E345656
|
entity |
| Predicate | hasSecularStatus |
P115489
|
FINISHED |
| Object | Imperial estate |
—
|
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 estate | Statement: [Medieval Prince-Bishopric of Magdeburg, hasSecularStatus, Imperial estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecularStatus Context triple: [Medieval Prince-Bishopric of Magdeburg, hasSecularStatus, Imperial estate]
-
A.
hasSecularRank
Indicates that one entity holds a specific position or level within a non-religious (secular) hierarchy relative to another entity.
-
B.
hasSecularAspects
Indicates that something includes or exhibits non-religious, worldly, or secular characteristics or dimensions.
-
C.
hasSecularUse
Indicates that something is used in a non-religious, worldly, or secular context or purpose.
-
D.
religiousStatus
Indicates the religious affiliation, role, or standing that an entity holds within a religious context.
-
E.
secularAuthorityHeldBy
Indicates that the specified entity holds or exercises non-religious (civil or governmental) authority over another entity.
- F. None of above. chosen
Provenance (4 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb98513b081908b230f6ac79c72ad |
completed | April 14, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69de657e174481909da0437556334a04 |
completed | April 14, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69de716d3aac8190aaa6dc1f099b86e8 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:29 a.m.