Triple
T32039237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Settimio |
E818176
|
entity |
| Predicate | functionAsSaint |
P133164
|
FINISHED |
| Object | spiritual protector of Jesi |
—
|
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: spiritual protector of Jesi | Statement: [Saint Settimio, functionAsSaint, spiritual protector of Jesi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionAsSaint Context triple: [Saint Settimio, functionAsSaint, spiritual protector of Jesi]
-
A.
typeOfSaint
Indicates that one entity is classified as a specific kind or category of saint in relation to another entity.
-
B.
mainSaint
chosen
Indicates that one entity is recognized as the principal or patron saint associated with another entity (such as a place, institution, or group).
-
C.
portraysAsSaint
Indicates that one entity depicts or represents another entity as a saintly, holy, or morally exemplary figure.
-
D.
functionInRitual
Indicates that an entity serves a specific role or performs a particular function within a ritual.
-
E.
eraOfReligiousFunction
Indicates the historical time period during which a religious role, office, or function was actively performed or held.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 12:19 a.m.