Triple

T24252592
Position Surface form Disambiguated ID Type / Status
Subject DBAG Class 484 E603570 entity
Predicate designedToMeetAccessibilityStandards P86683 FINISHED
Object yes 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: yes | Statement: [DBAG Class 484, designedToMeetAccessibilityStandards, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: designedToMeetAccessibilityStandards
Context triple: [DBAG Class 484, designedToMeetAccessibilityStandards, yes]
  • A. hasARIAcertification
    Indicates that an entity possesses an ARIA (Accessible Rich Internet Applications) certification attesting to compliance with relevant accessibility standards.
  • B. accessibilityFeatures
    Indicates the specific tools, settings, or design elements provided to make something usable or understandable for people with disabilities or diverse access needs.
  • C. isADACompliant
    Indicates that something meets the accessibility standards and requirements defined by the Americans with Disabilities Act (ADA).
  • D. designedToMeetRequirement chosen
    Indicates that something has been intentionally created or configured in order to satisfy a specified requirement.
  • E. accessible
    Indicates that one entity can be reached, entered, used, or understood by another entity, often without undue difficulty or barriers.
  • 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_69e29540da0481909a38bdae315b7a02 completed April 17, 2026, 8:17 p.m.
NER Named-entity recognition batch_69f28b8aff788190bb37fc8ab04bde00 completed April 29, 2026, 10:51 p.m.
PD Predicate disambiguation batch_69f1c450aa508190bc9d372a5f6ee47a completed April 29, 2026, 8:41 a.m.
Created at: April 18, 2026, 12:05 a.m.