Triple
T34220267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meadow Mari people |
E877903
|
entity |
| Predicate | traditionalRitualSite |
P90408
|
FINISHED |
| Object | sacred groves |
—
|
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: sacred groves | Statement: [Meadow Mari people, traditionalRitualSite, sacred groves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalRitualSite Context triple: [Meadow Mari people, traditionalRitualSite, sacred groves]
-
A.
ritualStructure
Indicates a relationship where an entity is a structure or built feature specifically used for performing rituals or ceremonial practices.
-
B.
mainLocationOfRituals
chosen
Indicates that a place serves as the primary setting where a group's rituals are regularly performed.
-
C.
ritualSignificance
Indicates that something holds special importance or meaning within a ritual or ceremonial context.
-
D.
ritualActivities
Indicates that one entity engages in, performs, or is associated with ritualistic or ceremonial activities in relation to another entity or context.
-
E.
ritualCentersOn
Indicates that a ritual is primarily focused on, organized around, or thematically centered on a particular entity, object, or concept.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff1c91bbac8190b84012dee1cb3b2c |
completed | May 9, 2026, 11:37 a.m. |
| PD | Predicate disambiguation | batch_69ff1c23ca508190bb5a435d765b7e53 |
completed | May 9, 2026, 11:36 a.m. |
Created at: May 1, 2026, 1:55 a.m.