Triple
T30963900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of Monreale |
E788897
|
entity |
| Predicate | episcopalInsignia |
P170851
|
FINISHED |
| Object | mitre |
—
|
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: mitre | Statement: [Bishop of Monreale, episcopalInsignia, mitre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: episcopalInsignia Context triple: [Bishop of Monreale, episcopalInsignia, mitre]
-
A.
hasEpiscopalSeal
Indicates that an entity possesses or is associated with a specific episcopal (bishop’s) seal.
-
B.
episcopalCharacter
Indicates that an entity possesses the status, authority, or qualities associated with a bishop within an ecclesiastical hierarchy.
-
C.
papalInsigniaElement
Indicates that something is an element or component of the insignia associated with the papacy.
-
D.
episcopalSeeOf
Indicates that one entity serves as the episcopal see (the official seat or jurisdictional center) of a bishop or similar ecclesiastical authority for another entity.
-
E.
usesEpiscopalGovernance
Indicates that an entity is organized or governed under an episcopal system, where authority is vested in bishops who oversee churches or regions.
- F. None of above. chosen
Provenance (4 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 8:54 p.m.