Triple
T35905328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tai Aiton people |
E1038455
|
entity |
| Predicate | performsFestival |
P116079
|
FINISHED |
| Object | Poi Sangken |
—
|
NE NERFINISHED |
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: Poi Sangken | Statement: [Tai Aiton people, performsFestival, Poi Sangken]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performsFestival Context triple: [Tai Aiton people, performsFestival, Poi Sangken]
-
A.
operatesFestival
Indicates that one entity manages and runs the organization or execution of a festival for another entity or in a particular context.
-
B.
determinesFestival
Indicates that one entity decides, defines, or selects which festival is applicable or will occur for another entity or context.
-
C.
festivalFunction
Indicates that an event serves as a festival or is functioning in the role of a festival within a given context.
-
D.
hasFestival
Indicates that a location, community, or entity hosts or holds a festival or celebratory event.
-
E.
festivalPresence
chosen
Indicates that an entity is present at, participates in, or is associated with a particular festival 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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff17be6ad48190963206f2619b1b28 |
completed | May 9, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69ff1724ba24819092c928fcbcb286ec |
completed | May 9, 2026, 11:14 a.m. |
Created at: May 3, 2026, 4:07 p.m.