Triple
T37185733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riihimäki railway station |
E921315
|
entity |
| Predicate | commuterLine |
P95592
|
FINISHED |
| Object | Helsinki commuter rail |
—
|
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: Helsinki commuter rail | Statement: [Riihimäki railway station, commuterLine, Helsinki commuter rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commuterLine Context triple: [Riihimäki railway station, commuterLine, Helsinki commuter rail]
-
A.
commuterRoute
Indicates a route that is regularly used by people traveling between home and work or other routine daily destinations.
-
B.
subwayLine
Indicates that there is a subway line connection or service relationship between the referenced entities.
-
C.
commuterCorridorFor
Indicates a route or area that serves as a primary pathway for regular travel between two locations, typically used by commuters.
-
D.
operatesCommuterServiceBetween
Indicates that an entity runs a commuter transportation service connecting two specified locations.
-
E.
servesCommuterRailLine
chosen
Indicates that a location or facility provides access to and is a stop or station for a commuter rail line.
- 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_69f76ea250bc819083f28d81de25cd0c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:15 p.m.