Triple

T7120149
Position Surface form Disambiguated ID Type / Status
Subject Park Street metro station E165927 entity
Predicate isBusyTransitHub P74351 FINISHED
Object true 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: true | Statement: [Park Street metro station, isBusyTransitHub, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isBusyTransitHub
Context triple: [Park Street metro station, isBusyTransitHub, true]
  • A. hasTransportHub
    Indicates that a location contains or serves as a central facility where multiple transport routes or modes connect for passenger or cargo movement.
  • B. isTransportHubType
    Indicates that something serves as or belongs to a particular category of transport hub (such as a station, port, or terminal).
  • C. isBusiestStationIn
    Indicates that a station has the highest level of activity (e.g., passenger or traffic volume) within a specified area or system.
  • D. isTransportHubBetween
    Indicates that a location functions as a central node facilitating transportation connections between two or more other places.
  • E. isMajorTransitPointFor chosen
    Indicates that a location serves as a primary hub or key node for the movement or transfer of people, goods, or vehicles within a transportation network.
  • 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_69c6888227bc8190a1394679e3116f90 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e61ca6a88190a0eb9f287e3b723c completed March 27, 2026, 8:18 p.m.
PD Predicate disambiguation batch_69c6e1c7289881909f3b533c384f9ed4 completed March 27, 2026, 8 p.m.
Created at: March 27, 2026, 2:43 p.m.