Triple

T23171833
Position Surface form Disambiguated ID Type / Status
Subject Biomedical District of Mirandola E578879 entity
Predicate hasTypicalStandard P1587 FINISHED
Object ISO 13485 compliance 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: ISO 13485 compliance | Statement: [Biomedical District of Mirandola, hasTypicalStandard, ISO 13485 compliance]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTypicalStandard
Context triple: [Biomedical District of Mirandola, hasTypicalStandard, ISO 13485 compliance]
  • A. usesStandard chosen
    Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
  • B. isStandard
    Indicates that something conforms to an established norm, specification, or commonly accepted rule.
  • C. isStandardOn
    Indicates that a particular feature, option, or component is included by default as part of another item, rather than being optional or extra.
  • D. isStandardOf
    Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
  • E. hasTypicalAppearance
    Indicates that an entity exhibits the standard or commonly expected visual form or look associated with its kind.
  • 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_69e245fd2a388190b814c0dfa15f7148 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18f3007108190bc3c831f81ae1dce completed April 29, 2026, 4:55 a.m.
PD Predicate disambiguation batch_69ef89ff76808190808ee4ad9dea776b completed April 27, 2026, 4:08 p.m.
Created at: April 17, 2026, 4:03 p.m.