Triple

T34317875
Position Surface form Disambiguated ID Type / Status
Subject Potrero Metro Station E880643 entity
Predicate hasTypeOfAccessibility P51863 FINISHED
Object partial accessibility 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: partial accessibility | Statement: [Potrero Metro Station, hasTypeOfAccessibility, partial accessibility]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTypeOfAccessibility
Context triple: [Potrero Metro Station, hasTypeOfAccessibility, partial accessibility]
  • A. hasAccessibleAccess
    Indicates that an entity provides a form of access that is usable and reachable under defined accessibility conditions or standards.
  • B. hasTypicalAccessibility
    Indicates that something normally has a particular level or type of accessibility or ease of access.
  • C. hasMemberAccessibility
    Indicates that a group, organization, or collection has specific conditions or provisions governing how members can access or participate in it.
  • D. isAccessible
    Indicates that one entity can be reached, used, or entered by another entity without obstruction or restriction.
  • E. typeOfAccess chosen
    Indicates the specific kind or level of access that one entity has to another (such as read, write, or execute permissions).
  • 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_69f349b9cd508190a996a616903b3e6d completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69ff27b125948190aced0fe0189fd39a completed May 9, 2026, 12:25 p.m.
PD Predicate disambiguation batch_69ff26c30a0481909ef6a54ded851e42 completed May 9, 2026, 12:21 p.m.
Created at: May 1, 2026, 1:57 a.m.