Triple
T21418413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paragbiele Festival |
E528366
|
entity |
| Predicate | ritualAspect |
P25858
|
FINISHED |
| Object | traditional 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: traditional rites | Statement: [Paragbiele Festival, ritualAspect, traditional rites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ritualAspect Context triple: [Paragbiele Festival, ritualAspect, traditional rites]
-
A.
ritualCategory
Indicates the classification relationship that assigns a ritual to a specific ritual type or category.
-
B.
ritualSignificance
Indicates that something holds special importance or meaning within a ritual or ceremonial context.
-
C.
ritualCharacteristics
chosen
Indicates the defining features, practices, or attributes that characterize a particular ritual.
-
D.
ritualSpecialist
Indicates that one entity serves as a designated expert or practitioner responsible for performing or overseeing rituals in relation to another entity or context.
-
E.
ritualActivities
Indicates that one entity engages in, performs, or is associated with ritualistic or ceremonial activities in relation to another entity or context.
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee62d29f948190b820c92014d1c53a |
completed | April 26, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:46 p.m.