Triple
T37341901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virgin of the Pillar |
E927059
|
entity |
| Predicate | hasLiturgicalRankInZaragoza |
P3655
|
FINISHED |
| Object | solemnity |
—
|
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: solemnity | Statement: [Virgin of the Pillar, hasLiturgicalRankInZaragoza, solemnity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiturgicalRankInZaragoza Context triple: [Virgin of the Pillar, hasLiturgicalRankInZaragoza, solemnity]
-
A.
hasLiturgicalRank
chosen
Indicates that an entity is assigned a specific status or level within a liturgical or religious ceremonial hierarchy.
-
B.
hasDiocesanRank
Indicates that an entity holds a specific hierarchical rank or status within a diocese.
-
C.
hasBasilicaRank
Indicates that an entity holds the ecclesiastical status or designation of a basilica within a religious hierarchy.
-
D.
hasClergyRankOver
Indicates that one clergy member holds a higher ecclesiastical rank or authority than another within a religious hierarchy.
-
E.
ecclesiasticalRank
Indicates the hierarchical religious office or clerical status that one entity holds within a church or ecclesiastical organization.
- 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_69f76eb4e8a881908bd40da28f36fc7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
Created at: May 3, 2026, 4:16 p.m.