Triple
T923509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samaveda |
E19932
|
entity |
| Predicate | cosmologyRole |
P20395
|
FINISHED |
| Object | supports ritual order (ṛta) |
—
|
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: supports ritual order (ṛta) | Statement: [Samaveda, cosmologyRole, supports ritual order (ṛta)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cosmologyRole Context triple: [Samaveda, cosmologyRole, supports ritual order (ṛta)]
-
A.
cosmicFunction
chosen
Indicates a relationship where an entity serves a fundamental or overarching role within a cosmic or universal system.
-
B.
roleInGeneralRelativity
Indicates the role, function, or significance an entity has within the framework, theory, or practice of general relativity.
-
C.
positionInCosmogony
Indicates the role or place an entity occupies within a culture’s creation or origin narrative of the universe.
-
D.
universe
Indicates that something pertains to, exists within, or is associated with the entirety of space, time, matter, and phenomena collectively referred to as the universe.
-
E.
cosmicFamily
Indicates a familial or kinship relationship that exists at a cosmic or universal scale between 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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b314f6fc81908a3ccc2e741e3c2b |
completed | March 1, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69a4b295b02481908e5f53bfcb83cc94 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.