Triple
T34186573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Phoenix |
E876977
|
entity |
| Predicate | pastoralCenterLocation |
P44557
|
FINISHED |
| Object | Phoenix, Arizona |
—
|
NE NERFINISHED |
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: Phoenix, Arizona | Statement: [Diocese of Phoenix, pastoralCenterLocation, Phoenix, Arizona]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pastoralCenterLocation Context triple: [Diocese of Phoenix, pastoralCenterLocation, Phoenix, Arizona]
-
A.
hasPastoralCenter
chosen
Indicates that an entity possesses or is associated with a pastoral center as one of its facilities or organizational components.
-
B.
pastoralWorkLocation
Indicates the place where a person carries out their pastoral or ministerial duties.
-
C.
isVillageCenterOf
Indicates that a location functions as the central or main hub area of a specified village.
-
D.
usesPastoralSetting
Indicates that the action or work is set in an idealized rural or countryside environment characteristic of pastoral themes.
-
E.
centralLocation
Indicates that one entity serves as the primary or central place associated with 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_69f349ae640c8190b9cd220b5368d8b6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7100a7898819092ba06f35251fc7c |
completed | May 3, 2026, 9:06 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.