Triple
T22683283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jkb |
E560838
|
entity |
| Predicate | hasStationCodeRole |
P149233
|
FINISHED |
| Object | identifies Jakobsberg railway station in timetables |
—
|
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: identifies Jakobsberg railway station in timetables | Statement: [Jkb, hasStationCodeRole, identifies Jakobsberg railway station in timetables]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStationCodeRole Context triple: [Jkb, hasStationCodeRole, identifies Jakobsberg railway station in timetables]
-
A.
hasStationCode
Indicates that an entity is associated with a specific station identification code.
-
B.
hasStationCodeSystem
Indicates that an entity uses or is associated with a particular system for assigning or managing station codes.
-
C.
hasStationCodeInternal
Indicates that an entity is associated with a specific internal station code used within a system or organization.
-
D.
isPassengerStationCode
Indicates that a given code is officially assigned to identify a particular passenger station.
-
E.
hasStationAt
Indicates that an entity maintains or operates a station located at a specified place.
- F. None of above. chosen
Provenance (4 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1786204d88190a837a5f04e16e94c |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:12 p.m.