Triple

T29285729
Position Surface form Disambiguated ID Type / Status
Subject Sullivan Square MBTA busway E742505 entity
Predicate connectedMode P51916 FINISHED
Object heavy rail rapid transit 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: heavy rail rapid transit | Statement: [Sullivan Square MBTA busway, connectedMode, heavy rail rapid transit]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: connectedMode
Context triple: [Sullivan Square MBTA busway, connectedMode, heavy rail rapid transit]
  • A. connectivityMode
    Indicates how two or more entities are linked or able to communicate with each other, such as the type or method of connection used between them.
  • B. connectsState
    Indicates a relationship where one entity serves as a link or conduit between different states, conditions, or statuses of another entity.
  • C. connectionStandard
    Indicates the technical standard or protocol that defines how a connection between entities is established and operates.
  • D. connectionTo
    Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
  • E. connectsWithMode chosen
    Indicates a relationship where one entity connects to another using a specified method, channel, or mode of connection.
  • 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_69f09121ed8c8190b4cb27be3619c262 completed April 28, 2026, 10:51 a.m.
NER Named-entity recognition batch_69fd91a5dad8819093eeeef527027890 completed May 8, 2026, 7:32 a.m.
PD Predicate disambiguation batch_69fd8f65fe9081908902500a3228d935 completed May 8, 2026, 7:23 a.m.
Created at: April 28, 2026, 12:58 p.m.