Triple

T17175266
Position Surface form Disambiguated ID Type / Status
Subject Calgary Transit E416842 entity
Predicate providesAccessibilityFeatures P80912 FINISHED
Object wheelchair-accessible buses 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: wheelchair-accessible buses | Statement: [Calgary Transit, providesAccessibilityFeatures, wheelchair-accessible buses]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: providesAccessibilityFeatures
Context triple: [Calgary Transit, providesAccessibilityFeatures, wheelchair-accessible buses]
  • A. providesAccessibility
    Indicates that one entity enables or improves access to another entity, resource, or service, removing or reducing barriers to its use.
  • B. 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.
  • C. featuresAbility
    Indicates that one entity possesses, includes, or provides a particular ability or capability associated with another entity.
  • D. providesFunctionalityOf
    Indicates that one entity supplies, implements, or makes available the capabilities or functions that are normally associated with another entity.
  • E. accessFeature
    Indicates that one entity is permitted to use or interact with a specific feature or capability of 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_69d886d5f34c8190b24564dfaa63f3fb completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3fc0cec448190b30466628a2ff23f completed April 18, 2026, 9:47 p.m.
PD Predicate disambiguation batch_69e383141ae0819096acd71683637cbc completed April 18, 2026, 1:11 p.m.
Created at: April 10, 2026, 5:37 a.m.