Triple

T68558
Position Surface form Disambiguated ID Type / Status
Subject Foggy Bottom–GWU station E1368 entity
Predicate hasStationManagerKiosk P3742 FINISHED
Object yes 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: yes | Statement: [Foggy Bottom–GWU station, hasStationManagerKiosk, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasStationManagerKiosk
Context triple: [Foggy Bottom–GWU station, hasStationManagerKiosk, yes]
  • A. hasStationCode
    Indicates that an entity is associated with a specific station identification code.
  • B. hasStationBuilding
    Indicates that a station is associated with or includes a station building as part of its facilities.
  • C. hasClerk
    Indicates that an entity is served, assisted, or managed by a clerk associated with it.
  • D. isOn
    Indicates that one entity is physically positioned above and in contact with the top surface of another entity.
  • E. isRailHubFor
    Indicates that a location functions as a central node or interchange point within a rail network for the referenced area, routes, or services.
  • 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_69a24c06b3bc8190aa4ac89026115efc completed Feb. 28, 2026, 1:59 a.m.
NER Named-entity recognition batch_69a24fd16c248190a6ee4cd96c388772 completed Feb. 28, 2026, 2:15 a.m.
PD Predicate disambiguation batch_69a24ea8cfd081908a26edad2473dde3 completed Feb. 28, 2026, 2:10 a.m.
PDg Predicate description generation batch_69a24fcf5a88819088c5fa4c08476358 completed Feb. 28, 2026, 2:15 a.m.
Created at: Feb. 28, 2026, 2:03 a.m.