Triple

T20126528
Position Surface form Disambiguated ID Type / Status
Subject Right Concentration E490771 entity
Predicate isCultivatedThrough P102095 FINISHED
Object jhāna 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: jhāna | Statement: [Right Concentration, isCultivatedThrough, jhāna]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isCultivatedThrough
Context triple: [Right Concentration, isCultivatedThrough, jhāna]
  • A. isCultivated
    Indicates that an entity is intentionally grown, managed, or maintained by humans rather than occurring or developing naturally without human intervention.
  • B. isCultivatedAs
    Indicates that one entity is intentionally grown, tended, or produced by another as a crop, resource, or cultivated organism.
  • C. cultivatedThrough chosen
    Indicates that something is developed, improved, or brought into existence by means of a specified method, practice, or process.
  • D. cultivatedSince
    Indicates that one entity has been intentionally grown, farmed, or maintained by another entity starting from a specified point in time.
  • E. cultivatedFor
    Indicates that one entity is intentionally grown, raised, or developed for the benefit, use, or purpose of 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_69da62651a0c8190a3e05e95e056a66b completed April 11, 2026, 3:01 p.m.
NER Named-entity recognition batch_69e6674223008190827c454fe7ac86f4 completed April 20, 2026, 5:49 p.m.
PD Predicate disambiguation batch_69e54cfb0d0081908e789b9b57e96668 completed April 19, 2026, 9:45 p.m.
Created at: April 11, 2026, 11:31 p.m.