Triple
T30494571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bx36 bus |
E775968
|
entity |
| Predicate | crosstownService |
P162379
|
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: [Bx36 bus, crosstownService, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crosstownService Context triple: [Bx36 bus, crosstownService, true]
-
A.
isCrosstown
chosen
Indicates that something (such as a route, trip, or connection) runs across a town or city, typically linking areas on opposite sides without passing through the central hub.
-
B.
coordinatesTransportationServicesWith
Indicates that one entity organizes and manages the alignment and collaboration of transportation services with another entity or set of entities.
-
C.
isMajorCrosstownRoute
Indicates that a route serves as a primary thoroughfare connecting significant areas across a town or city.
-
D.
commuterServiceTo
Indicates a transportation service that regularly carries commuters to a specified destination.
-
E.
midtownService
Indicates that a service operates in, serves, or is specifically associated with the Midtown area.
- 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 29, 2026, 8:14 p.m.