Triple

T2609868
Position Surface form Disambiguated ID Type / Status
Subject Tripitaka E58747 entity
Predicate VinayaPitakaFunction P30517 FINISHED
Object monastic discipline and rules 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: monastic discipline and rules | Statement: [Tripitaka, VinayaPitakaFunction, monastic discipline and rules]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: VinayaPitakaFunction
Context triple: [Tripitaka, VinayaPitakaFunction, monastic discipline and rules]
  • A. दोषसिद्धि
    Indicates a judicial relationship where an authority formally establishes and declares a person’s guilt for an alleged offense.
  • B. usesCodeOfCanons chosen
    Indicates that one entity applies, follows, or is governed by a specified code of canons (a formal set of rules or laws).
  • C. numberOfTractates
    Indicates the total count of tractates associated with a given entity or collection.
  • D. ecclesiasticalDocumentOf
    Indicates that one entity is an ecclesiastical (church-related) document that is issued by, belongs to, or is formally associated with another entity.
  • E. tookSannyasaFrom
    Indicates that one entity formally renounced worldly life and accepted the monastic or ascetic order under the guidance or authority 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_69ab4ac3523881909679750c9f8c2dec completed March 6, 2026, 9:44 p.m.
NER Named-entity recognition batch_69abd89325308190985598373eb0d296 completed March 7, 2026, 7:49 a.m.
PD Predicate disambiguation batch_69abd80cd7fc81909e9696db2919129f completed March 7, 2026, 7:47 a.m.
Created at: March 6, 2026, 9:50 p.m.