Triple
T6491121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brahma Upanishad |
E148037
|
entity |
| Predicate | scripturalFamily |
P11799
|
FINISHED |
| Object | Upanishadic corpus |
—
|
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: Upanishadic corpus | Statement: [Brahma Upanishad, scripturalFamily, Upanishadic corpus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scripturalFamily Context triple: [Brahma Upanishad, scripturalFamily, Upanishadic corpus]
-
A.
religiousFamilyBackground
Indicates that two entities are related through a shared or specified religious family upbringing or heritage.
-
B.
scripturalBasis
Indicates that one entity serves as the religious or scriptural foundation, support, or justification for another entity (such as a belief, practice, or doctrine).
-
C.
scripturalTheme
Indicates that one entity represents a central religious or theological theme expressed, discussed, or emphasized within a scriptural text or passage.
-
D.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
E.
scripturalCorpus
chosen
Indicates that one entity is a body of scriptural or sacred texts associated with, or serving as the canonical writings for, another entity.
- 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_69c009088f3081909cd467b05919de30 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a9a8d8481908d88e5c9f0c773f7 |
completed | March 22, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69c06740bebc81909d9d6956baa2bcb9 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:53 p.m.