Triple
T29307920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Station (Wichita, Kansas) |
E743147
|
entity |
| Predicate | servedTrainService |
P138983
|
FINISHED |
| Object | Amtrak Lone Star |
—
|
NE NERFINISHED |
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: Amtrak Lone Star | Statement: [Union Station (Wichita, Kansas), servedTrainService, Amtrak Lone Star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedTrainService Context triple: [Union Station (Wichita, Kansas), servedTrainService, Amtrak Lone Star]
-
A.
servedByNamedTrain
chosen
Indicates that a service, route, or journey is operated specifically by a train with a particular designated name.
-
B.
servedByRailroad
Indicates that a location or facility is provided with transportation or service by a railroad line or company.
-
C.
hasRailServiceAt
Indicates that a rail transport service operates at or serves a particular location or facility.
-
D.
isRailServiceOf
Indicates that a particular rail service operates for, belongs to, or is provided by a specified entity (such as a route, operator, or network).
-
E.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: April 28, 2026, 1:14 p.m.