Triple
T28662068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tullum Leucorum |
E725493
|
entity |
| Predicate | wasInDiocese |
P150177
|
FINISHED |
| Object | Diocese of Gaul |
—
|
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 Gaul | Statement: [Tullum Leucorum, wasInDiocese, Diocese of Gaul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasInDiocese Context triple: [Tullum Leucorum, wasInDiocese, Diocese of Gaul]
-
A.
servedInDiocese
Indicates that one entity held a role or performed official duties within the jurisdiction of a particular diocese.
-
B.
originallyInDiocese
chosen
Indicates that an entity (such as a parish, church, or territory) was first or formerly under the jurisdiction of a specified diocese.
-
C.
hasParentDiocese
Indicates that a diocese is hierarchically subordinate to, and administratively overseen by, a specific parent diocese.
-
D.
operatesWithinDiocese
Indicates that an entity carries out its functions or activities under the jurisdiction of a specified diocese.
-
E.
hasDiocesanStatus
Indicates that an ecclesiastical jurisdiction or entity holds official recognition and authority as a diocese within a church hierarchy.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 4:58 a.m.