Triple

T18035055
Position Surface form Disambiguated ID Type / Status
Subject 3rd Street/Convention Center station E431485 entity
Predicate hasADACompliance P52091 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: [3rd Street/Convention Center station, hasADACompliance, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasADACompliance
Context triple: [3rd Street/Convention Center station, hasADACompliance, yes]
  • A. isADACompliant chosen
    Indicates that something meets the accessibility standards and requirements defined by the Americans with Disabilities Act (ADA).
  • B. hasComplianceStatement
    Indicates that an entity is associated with a formal declaration that it adheres to specified rules, standards, or regulatory requirements.
  • C. hasARIAcertification
    Indicates that an entity possesses an ARIA (Accessible Rich Internet Applications) certification attesting to compliance with relevant accessibility standards.
  • D. indicatesComplianceWith
    Indicates that one entity conforms to, satisfies, or adheres to the rules, standards, or requirements specified by another entity or framework.
  • E. hasSafetyRegulationCompliance
    Indicates that an entity adheres to, satisfies, or is in conformity with specified safety regulations or standards.
  • 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_69d8b9050fb48190890155145deb0a66 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4be39a7348190a75735fe56c78fc3 completed April 19, 2026, 11:36 a.m.
PD Predicate disambiguation batch_69e3f908da508190a088aa837ea5b7af completed April 18, 2026, 9:35 p.m.
Created at: April 10, 2026, 10:25 a.m.