Triple

T22964248
Position Surface form Disambiguated ID Type / Status
Subject Broadway (Albany, New York) E570992 entity
Predicate isKeyRouteIn P31587 FINISHED
Object downtown Albany transportation network 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: downtown Albany transportation network | Statement: [Broadway (Albany, New York), isKeyRouteIn, downtown Albany transportation network]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isKeyRouteIn
Context triple: [Broadway (Albany, New York), isKeyRouteIn, downtown Albany transportation network]
  • A. isKeyRoute chosen
    Indicates that a route plays a primary or strategically important role within a network or system.
  • B. isRouteOn
    Indicates that one route is located on, follows along, or is aligned with another specified path or infrastructure.
  • C. isRouteFor
    Indicates that one entity serves as a path, course, or channel used for traveling, transporting, or connecting to another entity.
  • D. isInKey
    Indicates that something is located within, or belongs to, a specified key or key-based grouping in a structured context.
  • E. isStandardRouteOn
    Indicates that a particular route is the default or officially designated path used on a given transportation line or service.
  • 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_69e245b212a88190b5259caf51606084 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f181f763688190aab8f444a1a71577 completed April 29, 2026, 3:58 a.m.
PD Predicate disambiguation batch_69ef3b9101f48190a06c69dff26c6441 completed April 27, 2026, 10:33 a.m.
Created at: April 17, 2026, 3:47 p.m.