Triple
T18489974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archbishop of Quebec |
E451791
|
entity |
| Predicate | dateOfElevationToArchdiocese |
P83900
|
FINISHED |
| Object | 1819 |
—
|
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: 1819 | Statement: [Archbishop of Quebec, dateOfElevationToArchdiocese, 1819]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfElevationToArchdiocese Context triple: [Archbishop of Quebec, dateOfElevationToArchdiocese, 1819]
-
A.
elevatedToArchbishopDate
chosen
Indicates the date on which an individual was formally elevated to the rank or office of archbishop.
-
B.
elevatedToArchdioceseBy
Indicates that one ecclesiastical jurisdiction was raised in rank to an archdiocese by a particular authority or decision.
-
C.
establishedAsArchdiocese
Indicates that a diocese or ecclesiastical jurisdiction has been formally elevated or designated as an archdiocese.
-
D.
elevationToArchdiocese
Indicates that a diocese or ecclesiastical jurisdiction has been formally raised in status to become an archdiocese.
-
E.
establishedAsArchdioceseOn
Indicates that a religious jurisdiction was formally elevated to the status of an archdiocese on a specific date.
- 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e531db64b8819089f638718dddb1dc |
completed | April 19, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:35 a.m.