Triple

T12261935
Position Surface form Disambiguated ID Type / Status
Subject Asalha Bucha E292244 entity
Predicate observanceBy P51213 FINISHED
Object lay Buddhists 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: lay Buddhists | Statement: [Asalha Bucha, observanceBy, lay Buddhists]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: observanceBy
Context triple: [Asalha Bucha, observanceBy, lay Buddhists]
  • A. observance
    Indicates the performance or maintenance of a practice, rule, or custom in accordance with prescribed or expected standards.
  • B. observanceSetting
    Indicates the context, environment, or circumstances in which an observance (such as a ritual, ceremony, or practice) takes place.
  • C. observanceRequires
    Indicates that carrying out a particular observance or practice is contingent upon, or must be accompanied by, the fulfillment of a specified requirement or condition.
  • D. observanceVariesBy chosen
    Indicates that the way in which something is observed, practiced, or kept differs depending on a specified factor such as group, place, or time.
  • E. observanceDependsOnLaw
    Indicates that the performance or fulfillment of an observance is contingent upon, or determined by, a particular law or legal requirement.
  • 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_69d6ab6856488190b5d31178d5015f8e completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d9380a5e78819086bd4dfe9a83d1f5 completed April 10, 2026, 5:48 p.m.
PD Predicate disambiguation batch_69d91c4a66cc819083ce6fcaf5042af6 completed April 10, 2026, 3:50 p.m.
Created at: April 8, 2026, 9:52 p.m.