Triple

T30624423
Position Surface form Disambiguated ID Type / Status
Subject Bhikkhu E779532 entity
Predicate requiresPriorStatus P43873 FINISHED
Object novice monk (samanera) 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: novice monk (samanera) | Statement: [Bhikkhu, requiresPriorStatus, novice monk (samanera)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiresPriorStatus
Context triple: [Bhikkhu, requiresPriorStatus, novice monk (samanera)]
  • A. requiresStatus chosen
    Indicates that one entity can only proceed, be valid, or be applied if another entity has a specified status or condition.
  • B. requiresPriorJudicialApproval
    Indicates that an action or decision can only be taken if it has been previously reviewed and authorized by a judicial authority.
  • C. requiresPriorGradeNormally
    Indicates that one entity typically needs to have achieved a specified prior grade or level before another related action, status, or relationship can occur.
  • D. previouslyRequired
    Indicates that one entity was required or necessary before another entity, typically as a prerequisite condition or step.
  • E. requiredBy
    Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
  • 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_69f224a431548190a44ad9d088dbf91f completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fe21b0cba48190b56c39e9f1c0eafa completed May 8, 2026, 5:47 p.m.
PD Predicate disambiguation batch_69fe204576848190aecf204e2adba5dc completed May 8, 2026, 5:41 p.m.
Created at: April 29, 2026, 8:27 p.m.