Triple
T30376180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cardinal-Priest of San Cecilia |
E772694
|
entity |
| Predicate | isWithinDiocese |
P37811
|
FINISHED |
| Object | Diocese of Rome |
—
|
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: Diocese of Rome | Statement: [Cardinal-Priest of San Cecilia, isWithinDiocese, Diocese of Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWithinDiocese Context triple: [Cardinal-Priest of San Cecilia, isWithinDiocese, Diocese of Rome]
-
A.
operatesWithinDiocese
Indicates that an entity carries out its functions or activities under the jurisdiction of a specified diocese.
-
B.
hasParentDiocese
Indicates that a diocese is hierarchically subordinate to, and administratively overseen by, a specific parent diocese.
-
C.
isOnlyDioceseIn
Indicates that a diocese is the sole diocese within a specified territorial or organizational jurisdiction.
-
D.
hasDioceseEquivalent
Indicates that an entity possesses a jurisdictional unit that is functionally equivalent to a diocese, even if it has a different formal designation.
-
E.
servedInDiocese
chosen
Indicates that one entity held a role or performed official duties within the jurisdiction 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_69f2248e3444819081b05712dc6873de |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68513cbf881908ec5f924484b19b9 |
completed | May 2, 2026, 11:13 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8 p.m.