Triple
T4794737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sakha people |
E106683
|
entity |
| Predicate | YhyakhFestivalType |
P38636
|
FINISHED |
| Object | summer solstice 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: summer solstice festival | Statement: [Sakha people, YhyakhFestivalType, summer solstice festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: YhyakhFestivalType Context triple: [Sakha people, YhyakhFestivalType, summer solstice festival]
-
A.
hasFestivityType
Indicates that an event or celebration is classified as belonging to a particular type of festivity.
-
B.
festivalObserved
chosen
Indicates that a particular festival is celebrated, observed, or commemorated by an entity (such as a person, group, or community).
-
C.
determinesFestival
Indicates that one entity decides, defines, or selects which festival is applicable or will occur for another entity or context.
-
D.
festivalSeason
Indicates that a time period is designated or recognized as the season during which a particular festival or set of festivals takes place.
-
E.
exampleFestival
Indicates that an entity is an instance or example of a particular festival event or type of 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_69bd43f591c881909e5a532388b0f3f3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6b40c29c8190adab3503f8ba0145 |
completed | March 20, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69bd622f88188190a51d52ccfad3d2dd |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.