Triple
T11512562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tredozio |
E272948
|
entity |
| Predicate | hasFestiveEvent |
P3113
|
FINISHED |
| Object | local patron saint 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: local patron saint celebrations | Statement: [Tredozio, hasFestiveEvent, local patron saint celebrations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFestiveEvent Context triple: [Tredozio, hasFestiveEvent, local patron saint celebrations]
-
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.
hasFeastOrCommemoration
Indicates that a particular day, event, or context includes an associated religious feast, liturgical celebration, or commemorative observance.
-
D.
hasImportantHoliday
Indicates that an entity is associated with a holiday considered significant or special in some context.
-
E.
hasCulturalEvent
Indicates that a cultural event (such as a festival, performance, or exhibition) takes place in, is associated with, or is hosted by a given entity.
- 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d86db7af688190b68668eb39d382a8 |
completed | April 10, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.