Triple

T16039338
Position Surface form Disambiguated ID Type / Status
Subject Q (New York City Subway service) E389051 entity
Predicate introducedOnCurrentRouting P121706 FINISHED
Object January 1, 2017 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: January 1, 2017 | Statement: [Q (New York City Subway service), introducedOnCurrentRouting, January 1, 2017]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: introducedOnCurrentRouting
Context triple: [Q (New York City Subway service), introducedOnCurrentRouting, January 1, 2017]
  • A. locatedOnRouteTo
    Indicates that one entity lies along the path or course taken when traveling from a starting point to a specified destination.
  • B. operatedOnRoute
    Indicates that a transportation service or vehicle was active and provided service along a specified route.
  • C. supportsHierarchicalRouting
    Indicates that one entity enables or is compatible with routing that uses a multi-level or hierarchical structure of routing domains or paths.
  • D. usesFormerRouteOf
    Indicates that one route, service, or pathway currently follows all or part of the alignment or path that was previously used by another route.
  • E. supportsRouting
    Indicates that one entity provides the capability to determine and direct paths or routes for another entity’s traffic, requests, or messages.
  • F. None of above. chosen

Provenance (4 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_69d86dada3808190825d5f80d72fbe88 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e1ff63edb0819092cbb671967bbdcd completed April 17, 2026, 9:37 a.m.
PD Predicate disambiguation batch_69e1826f34c081908005bb736f1c485d completed April 17, 2026, 12:44 a.m.
PDg Predicate description generation batch_69e1ff5cd7e481908a29214139a3de2e completed April 17, 2026, 9:37 a.m.
Created at: April 10, 2026, 4:56 a.m.