Triple
T14815015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jalostotitlán |
E348288
|
entity |
| Predicate | hasPublicHolidayEvent |
P102818
|
FINISHED |
| Object | Holy Week celebrations |
—
|
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: Holy Week celebrations | Statement: [Jalostotitlán, hasPublicHolidayEvent, Holy Week celebrations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicHolidayEvent Context triple: [Jalostotitlán, hasPublicHolidayEvent, Holy Week celebrations]
-
A.
hasPublicHolidayOrFestival
chosen
Indicates that there exists a public holiday or festival associated with, occurring in, or relevant to the given entity.
-
B.
hasImportantHoliday
Indicates that an entity is associated with a holiday considered significant or special in some context.
-
C.
hasOfficialHoliday
Indicates that a particular date, event, or period is formally recognized as an official holiday by an authority or governing body.
-
D.
hasMunicipalHoliday
Indicates that a particular place or jurisdiction observes a specific municipal holiday as part of its official local calendar.
-
E.
hasCommonHoliday
Indicates that two entities share at least one holiday that is observed or celebrated in common.
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decfe0e89c81908c0e1fe2bc3ebcfc |
completed | April 14, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:49 a.m.