Triple
T4989359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diospolis |
E112089
|
entity |
| Predicate | wasChristianBishopric |
P43325
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Diospolis, wasChristianBishopric, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasChristianBishopric Context triple: [Diospolis, wasChristianBishopric, yes]
-
A.
wasPrinceBishopricUntil
Indicates that an entity functioned as a prince-bishopric up to (and including, or until) a specified point in time.
-
B.
establishedAsPrinceBishopric
Indicates that an entity was formally created or designated as a prince-bishopric, combining both secular princely authority and ecclesiastical bishopric status.
-
C.
hasBishopric
chosen
Indicates that an entity holds or is assigned a bishopric, i.e., the office, jurisdiction, or see of a bishop.
-
D.
isTitularChurchOf
Indicates that a particular church holds the official honorary title associated with a specific cardinal or ecclesiastical office.
-
E.
majorArchepiscopalSee
Indicates that one entity serves as the principal episcopal jurisdiction (major archiepiscopal see) governing or presiding over the other within a particular church or rite.
- 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_69bd441be7bc8190b530362d427b97d2 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74249a8c8190952680aee06a9286 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd71492dec8190af4c27a3043b35cc |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:34 p.m.