Triple
T34193663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medak Cathedral |
E877179
|
entity |
| Predicate | dioceseHeadquartersOf |
P37122
|
FINISHED |
| Object | Medak Diocese of the Church of South India |
—
|
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: Medak Diocese of the Church of South India | Statement: [Medak Cathedral, dioceseHeadquartersOf, Medak Diocese of the Church of South India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dioceseHeadquartersOf Context triple: [Medak Cathedral, dioceseHeadquartersOf, Medak Diocese of the Church of South India]
-
A.
dioceseGovernedStart
Indicates the point in time when a particular authority or leader began governing a specific diocese.
-
B.
administrativeDiocese
Indicates that one entity serves as the ecclesiastical administrative diocese responsible for the governance or oversight of another entity.
-
C.
dioceseErectedOn
Indicates the date or point in time when a diocese was formally established or created.
-
D.
dioceseBishop
Indicates that a person serves as the bishop (ecclesiastical leader) of a specified diocese.
-
E.
isDiocesanSeatOf
chosen
Indicates that a location serves as the central administrative seat or headquarters of a particular diocese.
- 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_69f349af20a4819089ac24d28f2d8112 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f710276a7c81909d292c0e73b48533 |
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.