Triple
T13026659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gembloux railway station |
E326324
|
entity |
| Predicate | railwayTrafficRole |
P107526
|
FINISHED |
| Object | regional stop |
—
|
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 stop | Statement: [Gembloux railway station, railwayTrafficRole, regional stop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayTrafficRole Context triple: [Gembloux railway station, railwayTrafficRole, regional stop]
-
A.
railwayLineRole
Indicates the specific functional role or purpose that a railway line serves within a rail network or transportation system.
-
B.
railwayTraffic
Indicates the presence, flow, or management of train movements along railway lines between locations.
-
C.
railNetworkRole
Indicates the specific function or responsibility an entity has within a rail network system.
-
D.
coordinatesRailTrafficWith
Indicates that one entity organizes and synchronizes rail operations or movements with another entity to ensure coordinated train traffic.
-
E.
railwayInfrastructureManager
Indicates that one entity is responsible for managing, maintaining, and operating the railway infrastructure used by another entity.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97efc07488190a15f3e41ea2db45c |
completed | April 10, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
| PDg | Predicate description generation | batch_69d97e3df2288190a7f27d31d248bb7f |
completed | April 10, 2026, 10:48 p.m. |
Created at: April 9, 2026, 8:53 p.m.