Triple
T30217658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sherdukpen |
E768251
|
entity |
| Predicate | festivalCulture |
P77637
|
FINISHED |
| Object | rich festival traditions |
—
|
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: rich festival traditions | Statement: [Sherdukpen, festivalCulture, rich festival traditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: festivalCulture Context triple: [Sherdukpen, festivalCulture, rich festival traditions]
-
A.
culturalScene
chosen
Indicates a relationship where an entity is associated with, participates in, or characterizes a particular cultural environment, milieu, or set of cultural activities.
-
B.
festivalFocus
Indicates that a festival is centered around, dedicated to, or thematically focused on a particular subject, activity, or feature.
-
C.
festivalCountry
Indicates the country in which a given festival takes place or is held.
-
D.
shareCulturalFestivals
Indicates that two or more entities participate in or observe the same cultural festivals or celebrations.
-
E.
festivalFeature
Indicates that a festival includes or showcases a particular element, activity, or attraction as one of its features.
- 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ff6fdf481908bf368299814159b |
completed | May 2, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:34 p.m.