Triple
T27793216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngmayem festival |
E701137
|
entity |
| Predicate | typeOfRites |
P76648
|
FINISHED |
| Object | agrarian rites |
—
|
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: agrarian rites | Statement: [Ngmayem festival, typeOfRites, agrarian rites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfRites Context triple: [Ngmayem festival, typeOfRites, agrarian rites]
-
A.
ritualCategory
chosen
Indicates the classification relationship that assigns a ritual to a specific ritual type or category.
-
B.
ritualsDirectedAt
Indicates that certain rituals are performed with a specific entity, object, or target as their intended focus or recipient.
-
C.
minorityRites
Indicates that certain rights, protections, or privileges are specifically granted to or held by a minority group in relation to a broader population or authority.
-
D.
ritualStructure
Indicates a relationship where an entity is a structure or built feature specifically used for performing rituals or ceremonial practices.
-
E.
ritualSpecialization
Indicates a relationship where an entity is specifically focused on, trained in, or primarily responsible for performing a particular type of ritual or set of ritual practices.
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: April 27, 2026, 5:29 p.m.