Triple
T37424805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathedral of San Bartolomeo |
E929959
|
entity |
| Predicate | hasRelicOrPatron |
—
|
GENERATED |
| Object | Saint Bartholomew |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelicOrPatron Context triple: [Cathedral of San Bartolomeo, hasRelicOrPatron, Saint Bartholomew]
-
A.
hasRelicsStatus
Indicates that an entity holds a particular status or condition specifically related to relics.
-
B.
containsRelic
chosen
Indicates that one entity holds, includes, or has within it a relic.
-
C.
hasPatronCharacter
Indicates that one entity serves as a patron, protector, or guiding figure for another entity.
-
D.
hasRelicType
Indicates that an entity is associated with, classified by, or possesses a specific type or category of relic.
-
E.
hasNotablePatron
Indicates that an entity is significantly supported, sponsored, or championed by a distinguished or influential patron.
- F. None of above.
Provenance (1 batch)
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_69f76ebf0f288190ba198a78341613b8 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.