Triple

T18866640
Position Surface form Disambiguated ID Type / Status
Subject Memphis Area Transit Authority E461454 entity
Predicate hasAccessibilityService P80912 FINISHED
Object paratransit for people with disabilities 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: paratransit for people with disabilities | Statement: [Memphis Area Transit Authority, hasAccessibilityService, paratransit for people with disabilities]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAccessibilityService
Context triple: [Memphis Area Transit Authority, hasAccessibilityService, paratransit for people with disabilities]
  • A. hasAccessibilityVariation
    Indicates that one entity differs from another in terms of accessibility features, conditions, or support.
  • B. hasAccessibleAccess
    Indicates that an entity provides a form of access that is usable and reachable under defined accessibility conditions or standards.
  • C. accessibilityFeatures chosen
    Indicates the specific tools, settings, or design elements provided to make something usable or understandable for people with disabilities or diverse access needs.
  • D. currentAccessibility
    Indicates the present state or level of how easily something can be accessed or used.
  • E. hasControlService
    Indicates that one entity provides or performs a control-related service for another entity.
  • 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_69d8dcfb7b9c8190854e7b171b98ea2e completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5c2a617548190be6044bf2c3de6d0 completed April 20, 2026, 6:07 a.m.
PD Predicate disambiguation batch_69e48d2166b88190add38de96cedc65c completed April 19, 2026, 8:06 a.m.
Created at: April 10, 2026, 11:57 a.m.