Triple
T24419950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omushkego |
E615696
|
entity |
| Predicate | hasSpiritualTraditions |
P24121
|
FINISHED |
| Object | land-based spirituality |
—
|
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: land-based spirituality | Statement: [Omushkego, hasSpiritualTraditions, land-based spirituality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpiritualTraditions Context triple: [Omushkego, hasSpiritualTraditions, land-based spirituality]
-
A.
hasSpiritualDimension
Indicates that something possesses or involves a non-material, spiritual, or transcendent aspect or quality.
-
B.
hasSpiritualLife
Indicates that an entity possesses or engages in a spiritual or religious inner life, practice, or orientation.
-
C.
religiousTraditions
chosen
Indicates a relationship where certain religious customs, practices, or belief systems are associated with or observed by an entity.
-
D.
spiritualityInfluencedBy
Indicates that one entity’s spirituality, spiritual beliefs, or practices are shaped, guided, or affected by another entity.
-
E.
hasSpiritualSource
Indicates that something originates from, is derived from, or is fundamentally grounded in a spiritual or non-material source.
- 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_69e2d7e9bfac8190a748952a90957106 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296a227d08190bd4e3e4832c5a205 |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:13 a.m.