Triple
T30108188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oriens prefecture |
E765187
|
entity |
| Predicate | includedDiocese |
P2740
|
FINISHED |
| Object | Diocese of the East |
—
|
NE NERFINISHED |
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: Diocese of the East | Statement: [Oriens prefecture, includedDiocese, Diocese of the East]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedDiocese Context triple: [Oriens prefecture, includedDiocese, Diocese of the East]
-
A.
linkedDiocese
Indicates a formal association or connection established between one diocese and another.
-
B.
administrativeDiocese
Indicates that one entity serves as the ecclesiastical administrative diocese responsible for the governance or oversight of another entity.
-
C.
includedBishopsFrom
Indicates that a group, document, or event contains or incorporates bishops originating from a specified source or location.
-
D.
parishesIncluded
Indicates that certain parishes are contained within, or form part of, a larger administrative, geographic, or organizational unit.
-
E.
diocese
chosen
Indicates that one entity serves as the ecclesiastical district or jurisdiction under the authority of a bishop to which the other entity is related or 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00532815c881908f10d9594458b3d7 |
completed | May 10, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_6a0052b9f030819081b8105bdcaf6d8f |
completed | May 10, 2026, 9:41 a.m. |
Created at: April 29, 2026, 7:10 p.m.