Triple
T6995200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishopric of Duisburg |
E162192
|
entity |
| Predicate | hadOfficialFunction |
P20953
|
FINISHED |
| Object | spiritual authority |
—
|
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: spiritual authority | Statement: [Bishopric of Duisburg, hadOfficialFunction, spiritual authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadOfficialFunction Context triple: [Bishopric of Duisburg, hadOfficialFunction, spiritual authority]
-
A.
hadJudicialFunction
Indicates that an entity exercised or was assigned an official judicial role, authority, or responsibility in relation to another entity or context.
-
B.
hadFunction
chosen
Indicates that an entity previously served or fulfilled a particular role, purpose, or function.
-
C.
hasCivicFunction
Indicates that an entity performs, is responsible for, or is associated with an official public or civic role, duty, or service.
-
D.
functionedBefore
Indicates that one entity was operational or in working order at an earlier time than another entity.
-
E.
hadExecutivePowerIn
Indicates that an entity held executive authority or governing power within a specified organization, institution, or jurisdiction during a certain period.
- 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_69c68857ffc08190857dc62cd5253777 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbec259c8190bb4cfbc1ff6fc786 |
completed | March 27, 2026, 7:35 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c4a18881908d267137daed828b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:32 p.m.