Triple

T6387169
Position Surface form Disambiguated ID Type / Status
Subject ASTRO E143728 entity
Predicate hasStandards P43031 FINISHED
Object quality and safety standards for radiation therapy practice 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: quality and safety standards for radiation therapy practice | Statement: [ASTRO, hasStandards, quality and safety standards for radiation therapy practice]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasStandards
Context triple: [ASTRO, hasStandards, quality and safety standards for radiation therapy practice]
  • A. hasSoftwareStandard
    Indicates that an entity conforms to, implements, or is governed by a specified software-related standard.
  • B. isStandardOf
    Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
  • C. standardsType chosen
    Indicates the classification or category of standards that apply to or are associated with an entity or activity.
  • D. hasCertificationStandard
    Indicates that an entity complies with, or is associated with, a specific certification standard.
  • E. usesStandard
    Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
  • 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_69c008dac1ec81909cef8157ccd69962 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c06869dfb88190aeb84c6c61414888 completed March 22, 2026, 10:08 p.m.
PD Predicate disambiguation batch_69c060eff524819094cee1c70a0c1ff4 completed March 22, 2026, 9:36 p.m.
Created at: March 22, 2026, 4:34 p.m.