Triple
T5266128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shabara Svamin |
E118939
|
entity |
| Predicate | inMimamsaCanon |
P977
|
FINISHED |
| Object | foundational commentator |
—
|
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: foundational commentator | Statement: [Shabara Svamin, inMimamsaCanon, foundational commentator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inMimamsaCanon Context triple: [Shabara Svamin, inMimamsaCanon, foundational commentator]
-
A.
inCanonOf
chosen
Indicates that one entity is officially recognized as part of the established canon or authoritative body of works associated with another entity.
-
B.
viewOnVedas
Indicates the stance, opinion, or interpretive perspective that one entity holds regarding the Vedas.
-
C.
associatedUpanishad
Indicates a relationship where something is linked or connected to a particular Upanishad as its source, reference, or context.
-
D.
दोषसिद्धि
Indicates a judicial relationship where an authority formally establishes and declares a person’s guilt for an alleged offense.
-
E.
inRamayana
Indicates that the subject participates in, appears within, or is otherwise part of the events or narrative of the Ramayana.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7d5a23908190a24e79d1b29d6fcf |
completed | March 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69bd77c71268819094f9f5203eed392d |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:51 p.m.