Triple
T26467023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tikkurila |
E665794
|
entity |
| Predicate | hasTransportHubType |
P121817
|
FINISHED |
| Object | railway station |
—
|
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: railway station | Statement: [Tikkurila, hasTransportHubType, railway station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransportHubType Context triple: [Tikkurila, hasTransportHubType, railway station]
-
A.
hasTransportHub
Indicates that a location contains or serves as a central facility where multiple transport routes or modes connect for passenger or cargo movement.
-
B.
isTransportHubType
Indicates that something serves as or belongs to a particular category of transport hub (such as a station, port, or terminal).
-
C.
isKeyTransportHubIn
Indicates that a location functions as a primary node for transporting people or goods within the specified area or network.
-
D.
isGroundTransportHubFor
Indicates that a location functions as a central node or facility for organizing, coordinating, or serving ground-based transportation for another place or set of routes.
-
E.
transportationHubType
chosen
Indicates the specific kind of transportation hub an entity is (e.g., airport, train station, bus terminal).
- 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 27, 2026, 12:16 a.m.