Triple
T30947970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Bourges |
E788450
|
entity |
| Predicate | reducedToDioceseIn |
P67823
|
FINISHED |
| Object | 1802 |
—
|
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: 1802 | Statement: [Diocese of Bourges, reducedToDioceseIn, 1802]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reducedToDioceseIn Context triple: [Diocese of Bourges, reducedToDioceseIn, 1802]
-
A.
dioceseMergedInto
chosen
Indicates that one diocese has been dissolved or reorganized and incorporated into another diocese, transferring its jurisdiction and authority to the latter.
-
B.
formerDiocese
Indicates that an entity was once a diocese but no longer holds that diocesan status.
-
C.
administrativeDiocese
Indicates that one entity serves as the ecclesiastical administrative diocese responsible for the governance or oversight of another entity.
-
D.
dioceseLater
Indicates that one diocese exists or is established later in time than another diocese.
-
E.
dioceseGovernedStart
Indicates the point in time when a particular authority or leader began governing a specific diocese.
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:53 p.m.