Triple
T22231799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Carroll |
E549484
|
entity |
| Predicate | elevatedToArchbishop |
P83900
|
FINISHED |
| Object | 1808-04-08 |
—
|
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: 1808-04-08 | Statement: [John Carroll, elevatedToArchbishop, 1808-04-08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevatedToArchbishop Context triple: [John Carroll, elevatedToArchbishop, 1808-04-08]
-
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.
appointedAsArchbishop
Indicates that an authority formally assigned a person to hold the office or role of an archbishop.
-
D.
elevatedToArcheparchy
Indicates that a church jurisdiction or eparchy has been raised in rank or status to that of an archeparchy.
-
E.
electedAsArchbishopOn
Indicates that an entity was chosen and formally appointed to the position of archbishop 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12bf3de648190986a734f19643a8c |
completed | April 28, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69e71b5177d881908f90abde14ada7dc |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:38 p.m.