Triple
T27867451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santísimo Cristo de Girón shrine |
E704394
|
entity |
| Predicate | hasSacredImage |
P171437
|
FINISHED |
| Object | image of Christ |
—
|
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: image of Christ | Statement: [Santísimo Cristo de Girón shrine, hasSacredImage, image of Christ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSacredImage Context triple: [Santísimo Cristo de Girón shrine, hasSacredImage, image of Christ]
-
A.
hasSacredSymbol
Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
-
B.
hasSacredPrecinct
Indicates that an entity possesses or contains a designated sacred area or precinct associated with religious or ritual significance.
-
C.
hasSacredNumber
Indicates that a particular number is regarded as sacred, holy, or spiritually significant in relation to an entity.
-
D.
hasSacredSpring
Indicates that one entity possesses, contains, or is associated with a spring regarded as sacred or holy.
-
E.
hasSacredFunction
Indicates that something serves a religious or holy role, purpose, or duty within a sacred context.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 27, 2026, 6:22 p.m.