Triple
T34378017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marysville, Kansas |
E882344
|
entity |
| Predicate | hasPonyExpressStation |
P105426
|
FINISHED |
| Object | Pony Express Home Station No. 1 |
—
|
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: Pony Express Home Station No. 1 | Statement: [Marysville, Kansas, hasPonyExpressStation, Pony Express Home Station No. 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPonyExpressStation Context triple: [Marysville, Kansas, hasPonyExpressStation, Pony Express Home Station No. 1]
-
A.
hasStationAt
chosen
Indicates that an entity maintains or operates a station located at a specified place.
-
B.
hasInterchangeStationWith
Indicates that two transportation lines, routes, or systems share a station where passengers can transfer between them.
-
C.
hasAmtrakStationStatus
Indicates whether and how an entity is served by an Amtrak station, such as its operational or service status.
-
D.
isStationOf
Indicates that a given location functions as a station (e.g., transport or service hub) associated with or serving a particular system, line, route, or organization.
-
E.
hasRailStation
Indicates that one entity possesses, contains, or is served by a rail station.
- 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_69f349bf5d7481908dd5da4cbdf74047 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff21cbd9108190a52c0ba42004c669 |
completed | May 9, 2026, noon |
| PD | Predicate disambiguation | batch_69ff1faea91881908c626c70bca5100a |
completed | May 9, 2026, 11:51 a.m. |
Created at: May 1, 2026, 1:59 a.m.