Triple
T9031908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phom Naga |
E216391
|
entity |
| Predicate | MonyuFestivalSignificance |
P25068
|
FINISHED |
| Object | agricultural festival |
—
|
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: agricultural festival | Statement: [Phom Naga, MonyuFestivalSignificance, agricultural festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MonyuFestivalSignificance Context triple: [Phom Naga, MonyuFestivalSignificance, agricultural festival]
-
A.
majorFestivalFunction
Indicates that an entity serves as a primary or central function, role, or activity within a major festival.
-
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.
ceremonySignificance
Indicates the importance, meaning, or role that a particular ceremony holds within a given context or for specific participants.
-
E.
hasFestivalImportance
chosen
Indicates that something holds notable significance, relevance, or prominence within the context of a festival or festive event.
- 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_69ca83d10b608190b2b2f8e0a7faaf14 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6a9f2c7481909b4a272183f20585 |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:08 p.m.