Triple
T29856816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apatani indigenous religion |
E758207
|
entity |
| Predicate | festivalFunction |
P168197
|
FINISHED |
| Object | ensure prosperity |
—
|
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: ensure prosperity | Statement: [Apatani indigenous religion, festivalFunction, ensure prosperity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: festivalFunction Context triple: [Apatani indigenous religion, festivalFunction, ensure prosperity]
-
A.
festivalSystem
Indicates a relationship where an entity is part of, managed by, or associated with a festival-related organizational or operational system.
-
B.
festivalFeature
Indicates that a festival includes or showcases a particular element, activity, or attraction as one of its features.
-
C.
festivalActivity
Indicates that an entity is an event, performance, or engagement that takes place as part of a festival’s organized program.
-
D.
festivalOrganiser
Indicates that one entity is responsible for planning, coordinating, or managing a festival for another entity or context.
-
E.
exampleFestival
Indicates that an entity is an instance or example of a particular festival event or type of festival.
- F. None of above. chosen
Provenance (4 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_69f6764cbaac81908d3eea5ae5833153 |
completed | May 2, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 5:46 p.m.