Triple
T28596935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stadium–Chinatown station |
E723799
|
entity |
| Predicate | connectedByBus |
P3791
|
FINISHED |
| Object | local bus routes on Expo Boulevard |
—
|
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: local bus routes on Expo Boulevard | Statement: [Stadium–Chinatown station, connectedByBus, local bus routes on Expo Boulevard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedByBus Context triple: [Stadium–Chinatown station, connectedByBus, local bus routes on Expo Boulevard]
-
A.
accessByBusFrom
Indicates that one location can be reached from another location using a bus as the mode of transportation.
-
B.
connectsToBusAt
Indicates that one entity has an access or transfer point where it links to a bus service at a specific location or stop.
-
C.
hasAdjacentBusStation
Indicates that one location has a bus station situated directly next to or very near it.
-
D.
groundTransportConnection
Indicates a transportation link between locations that is provided via land-based modes such as road or rail.
-
E.
hasPublicTransportConnection
chosen
Indicates that there is an available public transportation link or service connecting the related entities.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: April 28, 2026, 4:22 a.m.