Triple
T31452339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archbishopric of Magdeburg |
E802356
|
entity |
| Predicate | hadSecularPower |
P46562
|
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: [Archbishopric of Magdeburg, hadSecularPower, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadSecularPower Context triple: [Archbishopric of Magdeburg, hadSecularPower, yes]
-
A.
hadSecularAuthority
chosen
Indicates that an entity possessed or exercised non-religious, civil, or governmental authority over others or over a territory.
-
B.
hadExecutivePowerIn
Indicates that an entity held executive authority or governing power within a specified organization, institution, or jurisdiction during a certain period.
-
C.
hasSecularAspects
Indicates that something includes or exhibits non-religious, worldly, or secular characteristics or dimensions.
-
D.
secularAuthorityHeldBy
Indicates that the specified entity holds or exercises non-religious (civil or governmental) authority over another entity.
-
E.
hadNationalChurch
Indicates that a country or region recognized a particular church as its official or primary national religious institution.
- 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_69f348c678ac81908a2e950867619061 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:14 p.m.