Triple

T22092191
Position Surface form Disambiguated ID Type / Status
Subject Purusharthas E545937 entity
Predicate ultimateAimWithinFramework P64674 FINISHED
Object Moksha 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: Moksha | Statement: [Purusharthas, ultimateAimWithinFramework, Moksha]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ultimateAimWithinFramework
Context triple: [Purusharthas, ultimateAimWithinFramework, Moksha]
  • A. aimOf chosen
    Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
  • B. definesAimsOf
    Indicates that one entity specifies or establishes the goals, purposes, or intended outcomes of another entity.
  • C. goalOfRealization
    Indicates the intended outcome or objective that an action, process, or plan is meant to bring into reality or achieve.
  • D. goalAtEnd
    Indicates that a particular goal or objective holds true or is achieved at the final state or endpoint of a process, sequence, or event.
  • E. aimsToMeasure
    Indicates that one entity is intended or designed to quantify, assess, or evaluate another entity or property.
  • 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_69e11e36d03c8190a83a1ba802b7231b completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f128e6b1d881909bf0f4a52199354c completed April 28, 2026, 9:38 p.m.
PD Predicate disambiguation batch_69e71b20ec50819096ac196c798f8e3c completed April 21, 2026, 6:37 a.m.
Created at: April 16, 2026, 8:29 p.m.