Triple
T24766959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathédrale Notre-Dame-des-Pommiers de Sisteron |
E619610
|
entity |
| Predicate | hasDioceseRole |
P37811
|
FINISHED |
| Object | former cathedral church |
—
|
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: former cathedral church | Statement: [Cathédrale Notre-Dame-des-Pommiers de Sisteron, hasDioceseRole, former cathedral church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDioceseRole Context triple: [Cathédrale Notre-Dame-des-Pommiers de Sisteron, hasDioceseRole, former cathedral church]
-
A.
hasDioceseFunction
Indicates that an entity serves in a specific functional role or capacity within a diocese.
-
B.
hasDiocesanStatus
Indicates that an ecclesiastical jurisdiction or entity holds official recognition and authority as a diocese within a church hierarchy.
-
C.
operatesWithinDiocese
Indicates that an entity carries out its functions or activities under the jurisdiction of a specified diocese.
-
D.
servedInDiocese
chosen
Indicates that one entity held a role or performed official duties within the jurisdiction of a particular diocese.
-
E.
hasDiocesanRank
Indicates that an entity holds a specific hierarchical rank or status within a 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 18, 2026, 4:28 a.m.