Triple
T32483797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 22nd Street station |
E830183
|
entity |
| Predicate | hasConnectingBusRoutes |
P39381
|
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: [22nd Street station, hasConnectingBusRoutes, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConnectingBusRoutes Context triple: [22nd Street station, hasConnectingBusRoutes, yes]
-
A.
hasBusServices
chosen
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
-
B.
hasPublicTransportConnection
Indicates that there is an available public transportation link or service connecting the related entities.
-
C.
hasBusInterchange
Indicates that one transport-related entity includes, contains, or is associated with a bus interchange facility.
-
D.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
E.
hasBusPlatforms
Indicates that a location or facility is equipped with one or more designated platforms for boarding or alighting from buses.
- 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_69f3491ff3b48190b50a7fa00bb05b1f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:58 a.m.