Triple
T690721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Station (Los Angeles) |
E13384
|
entity |
| Predicate | busTerminalFor |
P1297
|
FINISHED |
| Object | intercity buses |
—
|
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: intercity buses | Statement: [Union Station (Los Angeles), busTerminalFor, intercity buses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: busTerminalFor Context triple: [Union Station (Los Angeles), busTerminalFor, intercity buses]
-
A.
terminusStation
Indicates that a station serves as the final endpoint or terminal stop for a given route or service.
-
B.
hasBusStation
Indicates that a place or area contains or is served by a bus station.
-
C.
publicTransitStop
Indicates that a location serves as a designated stop or station where public transit vehicles (such as buses, trains, or trams) pick up and drop off passengers.
-
D.
hasPassengerTerminal
chosen
Indicates that one entity possesses or is equipped with a passenger terminal used for boarding, alighting, or handling passengers.
-
E.
interchangeStation
Indicates a station where passengers can transfer between different routes, lines, or modes of transportation.
- 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_69a4933e0f98819097d22766c49b61b8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0ad379c81909003d35c63822780 |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d221d38819083c0adda81f59b07 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.