Triple
T21029430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kether |
E518025
|
entity |
| Predicate | associatedWithChakra |
P136330
|
FINISHED |
| Object | crown chakra |
—
|
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: crown chakra | Statement: [Kether, associatedWithChakra, crown chakra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithChakra Context triple: [Kether, associatedWithChakra, crown chakra]
-
A.
associatedChakra
chosen
Indicates a relationship where something is linked or corresponds to a particular chakra within a chakra system.
-
B.
associatedWithAcharya
Indicates a relationship in which an entity is connected, linked, or related in some relevant way to an acharya (a spiritual or scholarly teacher).
-
C.
associatedMystic
Indicates a relationship where one entity is linked or connected to another through a mystical, spiritual, or esoteric association.
-
D.
associatedWithYogi
Indicates a relationship in which an entity has a connection, link, or involvement with a yogi.
-
E.
associatedWithSoulsOf
Indicates a relationship in which something is connected, linked, or related specifically to the souls of certain entities.
- 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_69e0b503275c8190afd9a163f997c709 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc7fd3ec81908ac237047f9b0d7a |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:55 p.m.