Triple
T4824030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Durham |
E107778
|
entity |
| Predicate | historicalPrivilege |
P15548
|
FINISHED |
| Object | temporal authority of bishops |
—
|
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: temporal authority of bishops | Statement: [Diocese of Durham, historicalPrivilege, temporal authority of bishops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPrivilege Context triple: [Diocese of Durham, historicalPrivilege, temporal authority of bishops]
-
A.
historicalRightGranted
chosen
Indicates that a right or privilege was formally granted to an entity at some point in the past.
-
B.
historicalPass
Indicates that an entity has successfully completed or passed a historical event, period, or examination related to history.
-
C.
historicalCondition
Indicates that one entity represents a condition, state, or circumstance that applied to another entity at some point in the past.
-
D.
historicalCharacteristic
Indicates that an entity possesses a trait, feature, or quality that is rooted in or defined by its history or past events.
-
E.
historical
Indicates that the subject has existed, occurred, or been relevant in the past rather than in the present or future.
- 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_69bd43f9efa081908314cb3e94fa1695 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1fe130819087ae01309f96a0c8 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:24 p.m.