Triple
T32339052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sozopolis in Pisidia |
E826257
|
entity |
| Predicate | hasBishopricStatus |
P43325
|
FINISHED |
| Object | episcopal see |
—
|
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: episcopal see | Statement: [Sozopolis in Pisidia, hasBishopricStatus, episcopal see]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBishopricStatus Context triple: [Sozopolis in Pisidia, hasBishopricStatus, episcopal see]
-
A.
hasBishopric
chosen
Indicates that an entity holds or is assigned a bishopric, i.e., the office, jurisdiction, or see of a bishop.
-
B.
hasBishopricTitleDerivedFrom
Indicates that a bishopric’s official title is derived from, or based on, another specified name or title.
-
C.
hasDiocesanStatus
Indicates that an ecclesiastical jurisdiction or entity holds official recognition and authority as a diocese within a church hierarchy.
-
D.
hasSuffraganBishop
Indicates that one bishop holds the position of suffragan (subordinate or assistant) bishop in relation to another bishop or ecclesiastical authority.
-
E.
countryOfBishopric
Indicates the country in which a given bishopric (episcopal see or diocese) is located or to which it belongs.
- 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_69f34913d9048190befaa634025232be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 12:48 a.m.