Triple
T10128513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herington, Kansas |
E226275
|
entity |
| Predicate | railNetworkImportance |
P64887
|
FINISHED |
| Object | regional rail hub |
—
|
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: regional rail hub | Statement: [Herington, Kansas, railNetworkImportance, regional rail hub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railNetworkImportance Context triple: [Herington, Kansas, railNetworkImportance, regional rail hub]
-
A.
railNetworkRole
Indicates the specific function or responsibility an entity has within a rail network system.
-
B.
railroadNetwork
Indicates a relationship where locations are connected as part of the same system of railway lines and infrastructure used for train transport.
-
C.
railNetworkCenter
chosen
Indicates that a location functions as a central hub or focal point within a rail transportation network.
-
D.
railwaySignificance
Indicates the importance or role that a railway or rail-related feature has within a transportation network, region, or context.
-
E.
routeImportance
Indicates the relative significance or priority of a route compared to other possible routes, typically in terms of usefulness, relevance, or preference.
- 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_69ca843057b48190a86730167f5d6b98 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd2f0a0e881909267a83fbeb31f0c |
completed | April 2, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:05 p.m.