Triple
T917423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pope Leo XIII |
E19800
|
entity |
| Predicate | dioceseGovernedStart |
P22926
|
FINISHED |
| Object | 1846 |
—
|
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: 1846 | Statement: [Pope Leo XIII, dioceseGovernedStart, 1846]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dioceseGovernedStart Context triple: [Pope Leo XIII, dioceseGovernedStart, 1846]
-
A.
diocese
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.
-
B.
establishedAsDiocese
Indicates that an ecclesiastical jurisdiction was formally created or elevated to the status of a diocese.
-
C.
numberOfDioceses
Indicates the total count of dioceses associated with a given entity.
-
D.
isLargestDioceseOf
Indicates that one diocese is the largest, typically by area or population, within a specified ecclesiastical jurisdiction or region.
-
E.
episcopalSeeOf
Indicates that one entity serves as the episcopal see (the official seat or jurisdictional center) of a bishop or similar ecclesiastical authority for another entity.
- F. None of above. chosen
Provenance (4 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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b6755c488190b7f7848110e3ea2c |
completed | March 1, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69a4b292d3408190947cbc2f794cf8c5 |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b67499708190a65f24d1fd7e4ec5 |
completed | March 1, 2026, 9:58 p.m. |
Created at: March 1, 2026, 7:40 p.m.