Triple

T785605
Position Surface form Disambiguated ID Type / Status
Subject G train E16593 entity
Predicate accessibilityStatus P1710 FINISHED
Object varies by station 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: varies by station | Statement: [G train, accessibilityStatus, varies by station]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: accessibilityStatus
Context triple: [G train, accessibilityStatus, varies by station]
  • A. accessible chosen
    Indicates that one entity can be reached, entered, used, or understood by another entity, often without undue difficulty or barriers.
  • B. accessibleFrom
    Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
  • C. autonomyStatus
    Indicates the degree to which an entity operates independently or with self-governed control, without external direction or intervention.
  • D. adaptationStatus
    Indicates the current state or progress of how something has been adapted or adjusted in response to specific conditions, requirements, or contexts.
  • E. enabledBy
    Indicates that one entity functions as the cause, condition, or resource that makes it possible for another entity’s action, state, or capability to occur or be realized.
  • 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_69a4936ad1fc81908f190208059ccf78 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a76b0d6c8190a09b1a0bd4a6eeec completed March 1, 2026, 8:54 p.m.
PD Predicate disambiguation batch_69a4a50db97c8190a1c55673f4a357b4 completed March 1, 2026, 8:43 p.m.
Created at: March 1, 2026, 7:38 p.m.