Triple
T34345798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hill Mari people |
E881428
|
entity |
| Predicate | ritualSiteType |
P21627
|
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: [Hill Mari people, ritualSiteType, sacred groves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ritualSiteType Context triple: [Hill Mari people, ritualSiteType, sacred groves]
-
A.
religiousSiteType
Indicates the specific kind or category of religious site associated with an entity (e.g., church, mosque, temple).
-
B.
cultSite
chosen
Indicates a location that is or was used for religious or ritual worship activities.
-
C.
ritualStructure
Indicates a relationship where an entity is a structure or built feature specifically used for performing rituals or ceremonial practices.
-
D.
culturalSite
Indicates that one entity is recognized or designated as a cultural site associated with or located in relation to another entity.
-
E.
templeComplexFeature
Indicates that one entity is a structural or functional feature that forms part of a larger temple complex.
- 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_69f349bc55e881908c8e338ef76b0043 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:58 a.m.