Triple
T30796532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kumarghat railway station |
E784244
|
entity |
| Predicate | primaryRailAccessPointFor |
—
|
GENERATED |
| Object | Kailashahar |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRailAccessPointFor Context triple: [Kumarghat railway station, primaryRailAccessPointFor, Kailashahar]
-
A.
primaryRailLinkFor
Indicates that one entity serves as the main or principal rail connection or route for another entity.
-
B.
primaryTerminalFor
Indicates that one entity serves as the main or principal terminal associated with another entity.
-
C.
primaryCorridorServed
Indicates that a corridor is the main route or pathway served by a given service, facility, or entity.
-
D.
primaryAccessPoint
chosen
Indicates that one entity serves as the main or principal point through which another entity is accessed or entered.
-
E.
primaryHubFor
Indicates that one entity serves as the main central hub or core point of coordination for another entity or set of entities.
- F. None of above.
Provenance (1 batch)
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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:42 p.m.