Triple
T24484355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yoreme (Mayo) traditions |
E617464
|
entity |
| Predicate | centralFestival |
P41325
|
FINISHED |
| Object | Holy Week ceremonies |
—
|
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 ceremonies | Statement: [Yoreme (Mayo) traditions, centralFestival, Holy Week ceremonies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralFestival Context triple: [Yoreme (Mayo) traditions, centralFestival, Holy Week ceremonies]
-
A.
mainFestival
chosen
Indicates that an event is the primary or central festival associated with a particular context, place, or entity.
-
B.
majorFestivalFunction
Indicates that an entity serves as a primary or central function, role, or activity within a major festival.
-
C.
festivalFocus
Indicates that a festival is centered around, dedicated to, or thematically focused on a particular subject, activity, or feature.
-
D.
cityCenterStage
Indicates that an event, activity, or focus is taking place prominently in the central area of a city.
-
E.
mainFestivalHubFor
Indicates that one location serves as the primary central hub or focal point for a particular 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_69e2d7f3ae788190b683394db15f220e |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:21 a.m.