Triple
T33252412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Joseph Glennon |
E851285
|
entity |
| Predicate | appointedArchbishopOfStLouis |
P92918
|
FINISHED |
| Object | 1903 |
—
|
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: 1903 | Statement: [John Joseph Glennon, appointedArchbishopOfStLouis, 1903]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedArchbishopOfStLouis Context triple: [John Joseph Glennon, appointedArchbishopOfStLouis, 1903]
-
A.
archbishopOf
Indicates that a person holds the ecclesiastical office of archbishop in relation to a specific diocese, region, or church jurisdiction.
-
B.
appointedAsArchbishop
chosen
Indicates that an authority formally assigned a person to hold the office or role of an archbishop.
-
C.
formerArchbishop
Indicates that a person previously held the position or title of archbishop but no longer does.
-
D.
archbishopricPredecessor
Indicates that one entity previously held the position of archbishop immediately before another entity in the same archbishopric office.
-
E.
appointedAsBishopOfSiouxFallsBy
Indicates that one entity was formally appointed to the position of Bishop of Sioux Falls by another entity.
- 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_69f34963135c819084e7f1d483421f00 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 1, 2026, 1:31 a.m.