Triple
T2220220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tepeyac Hill |
E48122
|
entity |
| Predicate | pilgrimagePeakDate |
P32543
|
FINISHED |
| Object | 12 December |
—
|
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: 12 December | Statement: [Tepeyac Hill, pilgrimagePeakDate, 12 December]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pilgrimagePeakDate Context triple: [Tepeyac Hill, pilgrimagePeakDate, 12 December]
-
A.
hasPilgrimagePeak
Indicates that a place or route is associated with a specific peak that serves as a destination or focal point for religious or spiritual pilgrimage.
-
B.
pilgrimageAssociatedWith
Indicates a relationship where a pilgrimage is connected or related to a particular entity, such as a place, person, event, or religious tradition.
-
C.
pilgrimageSeason
chosen
Indicates the time period or season during which religious pilgrimages customarily take place.
-
D.
isPilgrimageDestination
Indicates that a place serves as a destination specifically visited by people undertaking a religious or spiritual pilgrimage.
-
E.
pilgrimagePractice
Indicates that an entity engages in, prescribes, or is associated with the religious act of undertaking a pilgrimage as a spiritual practice.
- 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_69a88aa1ee708190862c8c378c41e9eb |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc01386588190a9507f2969a201ca |
completed | March 7, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69abbdac31d8819092d17815e11921e9 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.