Triple
T26512011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christ of La Laguna |
E669708
|
entity |
| Predicate | isPatronImageOf |
P160149
|
FINISHED |
| Object | San Cristóbal de La Laguna |
—
|
NE NERFINISHED |
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: San Cristóbal de La Laguna | Statement: [Christ of La Laguna, isPatronImageOf, San Cristóbal de La Laguna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPatronImageOf Context triple: [Christ of La Laguna, isPatronImageOf, San Cristóbal de La Laguna]
-
A.
recognizedAsCoPatronBy
Indicates that an entity is acknowledged or designated as a co-patron by another entity.
-
B.
usedAsPatronOf
Indicates that one entity serves as a patron or sponsor for another, providing support, endorsement, or backing.
-
C.
isImageOf
chosen
Indicates that one entity is a visual depiction or representation of another entity.
-
D.
coPatron
Indicates a relationship where two or more entities share joint responsibility or role as patrons supporting the same person, group, or endeavor.
-
E.
hasPatronageOver
Indicates that one entity serves as a patron, sponsor, or protector for another, exercising support, guidance, or authority over it.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61392ec5081909382ace560650d77 |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:21 a.m.