Triple
T6348054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Relics of Saint Gaudentius |
E142794
|
entity |
| Predicate | hasDevotee |
P8505
|
FINISHED |
| Object | Catholic faithful |
—
|
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: Catholic faithful | Statement: [Relics of Saint Gaudentius, hasDevotee, Catholic faithful]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDevotee Context triple: [Relics of Saint Gaudentius, hasDevotee, Catholic faithful]
-
A.
associatedDevotion
Indicates a relationship where one entity is linked to or characterized by a particular devotion, dedication, or religious/spiritual practice connected to another entity.
-
B.
devoteesSeek
Indicates that devoted followers actively seek out, pursue, or strive to approach the object of their devotion.
-
C.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
D.
praysTo
Indicates that one entity directs a prayer, supplication, or act of worship toward another entity as its spiritual or divine recipient.
-
E.
veneratedBy
chosen
Indicates that one entity is regarded with deep respect, reverence, or worship by another entity.
- 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_69c008d6dcbc8190aa1c2f1fd8916b42 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c067ba2c64819094fa38bb2aeffa6c |
completed | March 22, 2026, 10:05 p.m. |
| PD | Predicate disambiguation | batch_69c060ea1a988190889e47b7e0c819b8 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:31 p.m.