Triple

T2280981
Position Surface form Disambiguated ID Type / Status
Subject Shravikas E51277 entity
Predicate moralExpectation P36235 FINISHED
Object to observe anuvratas (small vows) 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: to observe anuvratas (small vows) | Statement: [Shravikas, moralExpectation, to observe anuvratas (small vows)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: moralExpectation
Context triple: [Shravikas, moralExpectation, to observe anuvratas (small vows)]
  • A. moralImplication
    Indicates that one situation, action, or state of affairs entails or suggests a particular moral judgment, obligation, or ethical consequence.
  • B. derivesMoralityFrom
    Indicates that one entity bases or grounds its moral principles, judgments, or ethical framework on another entity.
  • C. moralStatus
    Indicates the ethical standing or degree of moral consideration that one entity has in relation to another.
  • D. moralTheme
    Indicates that a work, event, or situation embodies or conveys a particular ethical lesson, value, or moral principle.
  • E. hasMoralPerspective
    Indicates that an entity holds or applies a particular moral or ethical viewpoint in evaluating actions, situations, or other entities.
  • F. None of above. chosen

Provenance (4 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_69a88b08e4308190bdac9aebcca1c91a completed March 4, 2026, 7:42 p.m.
NER Named-entity recognition batch_69abc21ac3d48190abef254e1c3f45e8 completed March 7, 2026, 6:13 a.m.
PD Predicate disambiguation batch_69abbdb9aa3c819088d0316c5269a1c2 completed March 7, 2026, 5:55 a.m.
PDg Predicate description generation batch_69abbe4368a88190956bc9ee89c0fd1f completed March 7, 2026, 5:57 a.m.
Created at: March 4, 2026, 7:48 p.m.