Triple
T25730204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sukkur railway station |
E645218
|
entity |
| Predicate | railwayTrafficFunction |
P33182
|
FINISHED |
| Object | freight services |
—
|
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: freight services | Statement: [Sukkur railway station, railwayTrafficFunction, freight services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayTrafficFunction Context triple: [Sukkur railway station, railwayTrafficFunction, freight services]
-
A.
railwayTraffic
Indicates the presence, flow, or management of train movements along railway lines between locations.
-
B.
railwayTrafficRole
Indicates the specific function or responsibility an entity has within the operation, management, or control of railway traffic.
-
C.
railwayTrafficDirection
Indicates the customary side of the track on which trains are operated or expected to run within a given railway system or segment.
-
D.
coordinatesRailTrafficWith
Indicates that one entity organizes and synchronizes rail operations or movements with another entity to ensure coordinated train traffic.
-
E.
railwayLineUsage
chosen
Indicates how a railway line is used, such as the type or purpose of traffic or operations it supports.
- 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_69e77e85254081908d79ee4e8715f283 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 21, 2026, 11:12 p.m.