Triple
T29856390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adi community |
E758198
|
entity |
| Predicate | stateRecognizedFestival |
P38636
|
FINISHED |
| Object | Solung |
—
|
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: Solung | Statement: [Adi community, stateRecognizedFestival, Solung]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateRecognizedFestival Context triple: [Adi community, stateRecognizedFestival, Solung]
-
A.
determinesFestival
Indicates that one entity decides, defines, or selects which festival is applicable or will occur for another entity or context.
-
B.
festivalStatus
Indicates the current state or condition of a festival, such as whether it is planned, ongoing, postponed, or completed.
-
C.
festivalRecognition
Indicates that an entity has been officially acknowledged, selected, or honored by a festival (e.g., through selection, nomination, or award).
-
D.
festivalObserved
chosen
Indicates that a particular festival is celebrated, observed, or commemorated by an entity (such as a person, group, or community).
-
E.
festivalSystem
Indicates a relationship where an entity is part of, managed by, or associated with a festival-related organizational or operational system.
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: April 29, 2026, 5:46 p.m.