Triple
T33396920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles J. Chaput |
E855196
|
entity |
| Predicate | appointedAsArchbishopOfPhiladelphia |
P92918
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Charles J. Chaput, appointedAsArchbishopOfPhiladelphia, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedAsArchbishopOfPhiladelphia Context triple: [Charles J. Chaput, appointedAsArchbishopOfPhiladelphia, 2011]
-
A.
installationAsArchbishopOfPhiladelphia
Indicates the event in which a person formally assumes the office and duties of Archbishop of Philadelphia.
-
B.
appointedAsArchbishop
chosen
Indicates that an authority formally assigned a person to hold the office or role of an archbishop.
-
C.
appointedAsArchbishopOfDenver
Indicates that a person has been formally appointed to serve in the role of Archbishop of Denver.
-
D.
appointedAsArchbishopOfBostonBy
Indicates that one entity formally appointed another entity to the position of Archbishop of Boston.
-
E.
appointedAsArchbishopOfNewYorkOn
Indicates that a person was formally appointed to the position of Archbishop of New York 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: May 1, 2026, 1:35 a.m.