Triple

T4300637
Position Surface form Disambiguated ID Type / Status
Subject Market Street tram stop E99825 entity
Predicate isKeyInterchange P31316 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: [Market Street tram stop, isKeyInterchange, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isKeyInterchange
Context triple: [Market Street tram stop, isKeyInterchange, yes]
  • A. isKeyInterchangeFor
    Indicates that one location or facility serves as a primary transfer point connecting major routes, lines, or modes of transport for another.
  • B. isInterchange
    Indicates that two entities can be substituted or exchanged for one another without affecting the relevant system, function, or outcome.
  • C. isKeyTransitHub chosen
    Indicates that a location functions as a major transfer point where multiple transportation routes or modes intersect and a high volume of passenger or cargo movement is concentrated.
  • D. keyAgreement
    Indicates that two or more parties participate in a cryptographic process to establish a shared secret key for secure communication.
  • E. isKeyEndpointOf
    Indicates that one endpoint in a connection, link, or structure serves as the primary or designated key endpoint of the other.
  • 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_69b345528ebc8190b5abc7e95094792d completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b3509e8cb481909ccca7992aac31a3 completed March 12, 2026, 11:47 p.m.
PD Predicate disambiguation batch_69b347fe55a88190b77bab0c0f38e1aa completed March 12, 2026, 11:10 p.m.
Created at: March 12, 2026, 11:08 p.m.