Triple
T25804020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erzya people |
E649913
|
entity |
| Predicate | traditionalReligionPlace |
P175289
|
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: [Erzya people, traditionalReligionPlace, sacred groves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalReligionPlace Context triple: [Erzya people, traditionalReligionPlace, sacred groves]
-
A.
inReligiousStructure
Indicates that one entity is located within or inside a building or structure used for religious purposes.
-
B.
religiousHouse
Indicates that an entity is a religious institution or building used for worship, residence, or activities of a religious community.
-
C.
declaredReligiousMissionPlace
Indicates that an entity has formally stated or designated a particular place as the location or focus of its religious mission.
-
D.
hasPlaceOfWorship
Indicates that an entity possesses, contains, or is associated with a designated location used for religious or spiritual worship.
-
E.
isPlaceOfWorshipFor
Indicates that a location serves as a site where members of a particular religion or belief system perform worship or religious practices.
- 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6d1d916f881909575c2b22c416a5b |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d0d331dc8190be5aa6bfc6365e67 |
completed | May 3, 2026, 4:36 a.m. |
Created at: April 22, 2026, 6:44 a.m.