Triple
T538899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archdiocese of New York |
E12385
|
entity |
| Predicate | elevatedToArchdiocese |
P3787
|
FINISHED |
| Object | 1850 |
—
|
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: 1850 | Statement: [Archdiocese of New York, elevatedToArchdiocese, 1850]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevatedToArchdiocese Context triple: [Archdiocese of New York, elevatedToArchdiocese, 1850]
-
A.
archbishopOf
Indicates that a person holds the ecclesiastical office of archbishop in relation to a specific diocese, region, or church jurisdiction.
-
B.
ecclesiasticalLevel
Indicates the hierarchical rank or status of an entity within an ecclesiastical (church) organization.
-
C.
elevatedTo
chosen
Indicates that one entity is promoted or raised to a higher rank, status, position, or level relative to another.
-
D.
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.
-
E.
consecratedBy
Indicates that one entity has been formally made sacred, dedicated, or set apart for religious use through a ritual or act performed 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b67c308190a1a225ab7c4b74c6 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.