Triple
T34307508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Pedro y San Pablo Ayutla |
E880348
|
entity |
| Predicate | hasFestivities |
P3113
|
FINISHED |
| Object | Catholic religious festivals |
—
|
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: Catholic religious festivals | Statement: [San Pedro y San Pablo Ayutla, hasFestivities, Catholic religious festivals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFestivities Context triple: [San Pedro y San Pablo Ayutla, hasFestivities, Catholic religious festivals]
-
A.
hasFestival
chosen
Indicates that a location, community, or entity hosts or holds a festival or celebratory event.
-
B.
hasFestivalPeriod
Indicates that there is a specific time period during which a festival or celebratory event takes place.
-
C.
hasFestivityType
Indicates that an event or celebration is classified as belonging to a particular type of festivity.
-
D.
hasPublicHolidayOrFestival
Indicates that there exists a public holiday or festival associated with, occurring in, or relevant to the given entity.
-
E.
hasFestivalSection
Indicates that something includes or is associated with a specific section or category within a festival.
- 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_69f349b8bb6c8190ad12a7957a574f04 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 1, 2026, 1:57 a.m.