Triple
T2220219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tepeyac Hill |
E48122
|
entity |
| Predicate | devotionBegan |
P19545
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [Tepeyac Hill, devotionBegan, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: devotionBegan Context triple: [Tepeyac Hill, devotionBegan, 16th century]
-
A.
associatedDevotion
Indicates a relationship where one entity is linked to or characterized by a particular devotion, dedication, or religious/spiritual practice connected to another entity.
-
B.
tookReligiousVowsOn
Indicates that an entity formally committed to religious vows on a specific date or occasion.
-
C.
consecratedBy
Indicates that one entity has been formally made sacred, dedicated, or set apart for religious use through a ritual or act performed by another entity.
-
D.
began
chosen
Indicates that one entity initiated or started an action, event, or state involving another entity or context.
-
E.
consecrated
Indicates that an entity has been formally dedicated or made sacred for a religious or holy purpose.
- 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.