Triple
T36307527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Digo |
E893979
|
entity |
| Predicate | usesSacredSites |
P916
|
FINISHED |
| Object | kaya forests |
—
|
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: kaya forests | Statement: [Digo, usesSacredSites, kaya forests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSacredSites Context triple: [Digo, usesSacredSites, kaya forests]
-
A.
hasSpiritualSitesIn
Indicates that one entity possesses or contains spiritual or religious sites located within the boundaries of another entity.
-
B.
hasSacredPrecinct
Indicates that an entity possesses or contains a designated sacred area or precinct associated with religious or ritual significance.
-
C.
sacredTo
Indicates that one entity is regarded as holy, revered, or dedicated in honor of another entity, such as a deity, person, or concept.
-
D.
sacredHill
Indicates that a hill holds religious or spiritual significance within a belief system or tradition.
-
E.
hasReligiousSite
chosen
Indicates that a location or entity possesses, contains, or is associated with a religious site such as a temple, church, mosque, shrine, or similar place of worship.
- 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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: May 3, 2026, 4:09 p.m.