Triple
T23793762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Builsa |
E588476
|
entity |
| Predicate | FeokFestivalSignificance |
P118766
|
FINISHED |
| Object | celebration of successful harvest |
—
|
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: celebration of successful harvest | Statement: [Builsa, FeokFestivalSignificance, celebration of successful harvest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FeokFestivalSignificance Context triple: [Builsa, FeokFestivalSignificance, celebration of successful harvest]
-
A.
feastSignificance
chosen
Indicates the cultural, religious, or social importance attributed to a particular feast or celebratory meal.
-
B.
festivalObserved
Indicates that a particular festival is celebrated, observed, or commemorated by an entity (such as a person, group, or community).
-
C.
festivalDay
Indicates that a given day is designated as a festival or celebration day within a particular context or calendar.
-
D.
majorFestivalFunction
Indicates that an entity serves as a primary or central function, role, or activity within a major festival.
-
E.
festivalFocus
Indicates that a festival is centered around, dedicated to, or thematically focused on a particular subject, activity, or feature.
- 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_69e25d15db58819092ac1e6791696fd9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c6da693481908194cbc9d6a0bfef |
completed | April 29, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:42 p.m.