Triple
T24512236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leszno railway station |
E606255
|
entity |
| Predicate | railwayStationCodeCountry |
P156564
|
FINISHED |
| Object | PL |
—
|
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: PL | Statement: [Leszno railway station, railwayStationCodeCountry, PL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayStationCodeCountry Context triple: [Leszno railway station, railwayStationCodeCountry, PL]
-
A.
railwayStationInCountry
Indicates that a railway station is located within the borders of a specified country.
-
B.
railwayStationCodeFor
Indicates that one entity is the designated railway station code corresponding to a particular railway station.
-
C.
isMainInternationalRailStopOf
Indicates that a location serves as the primary international railway stop or station for a given area, route, or settlement.
-
D.
otherRailwayStation
Indicates a relationship where one railway station is associated with another as a distinct but related station, such as an alternative, nearby, or counterpart station.
-
E.
hasRailwayStationRole
Indicates that an entity holds or is assigned a specific functional role or capacity within the operation or management of a railway station.
- 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_69e2c4c725148190a4e41577c5cb409c |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2a9d795288190916368e3cec1f666 |
completed | April 30, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:24 a.m.