Triple
T37688913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khalsa |
E938448
|
entity |
| Predicate | hasSpiritualMother |
P62185
|
FINISHED |
| Object | Mata Sahib Devan |
—
|
NE NERFINISHED |
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: Mata Sahib Devan | Statement: [Khalsa, hasSpiritualMother, Mata Sahib Devan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpiritualMother Context triple: [Khalsa, hasSpiritualMother, Mata Sahib Devan]
-
A.
hasSpiritualHead
Indicates that one entity serves as the primary religious or spiritual leader or authority for another entity.
-
B.
hasParentDeity
Indicates that one deity is the parent (progenitor or creator) of another deity.
-
C.
hasSpiritualLife
Indicates that an entity possesses or engages in a spiritual or religious inner life, practice, or orientation.
-
D.
hasSpiritualSource
Indicates that something originates from, is derived from, or is fundamentally grounded in a spiritual or non-material source.
-
E.
spiritualSonOf
chosen
Indicates a relationship where one person is regarded as the spiritual or religious protégé, disciple, or mentee of another, akin to a parent–child bond in a non-biological, faith-based context.
- 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_69f76ed881408190bc62a969530a4a53 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff0b6bc4a88190bf1d38c6ea26bcdc |
completed | May 9, 2026, 10:24 a.m. |
| PD | Predicate disambiguation | batch_69ff082a22f4819095ded971dbd8ea7b |
completed | May 9, 2026, 10:10 a.m. |
Created at: May 3, 2026, 4:18 p.m.