Triple
T31042824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Worms |
E791041
|
entity |
| Predicate | secularAuthorityType |
P115489
|
FINISHED |
| Object | Prince-bishop |
—
|
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-bishop | Statement: [Diocese of Worms, secularAuthorityType, Prince-bishop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secularAuthorityType Context triple: [Diocese of Worms, secularAuthorityType, Prince-bishop]
-
A.
secularAuthorityHeldBy
Indicates that the specified entity holds or exercises non-religious (civil or governmental) authority over another entity.
-
B.
religiousAuthorityStatus
Indicates the role or level of recognized authority an entity holds within a religious or spiritual hierarchy.
-
C.
hasSecularStatus
chosen
Indicates that an entity holds a non-religious, secular standing or classification within a given context.
-
D.
ecclesiasticalType
Indicates the specific ecclesiastical category or classification that applies to a religious entity within a church hierarchy.
-
E.
religiousCanonType
Indicates the specific category or type of religious canon to which a text, rule, or tradition belongs.
- 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:59 p.m.