Triple
T20213582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barddhaman Junction |
E493553
|
entity |
| Predicate | stateRailwayNetworkRole |
P5885
|
FINISHED |
| Object | major junction in West Bengal |
—
|
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: major junction in West Bengal | Statement: [Barddhaman Junction, stateRailwayNetworkRole, major junction in West Bengal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateRailwayNetworkRole Context triple: [Barddhaman Junction, stateRailwayNetworkRole, major junction in West Bengal]
-
A.
railNetworkRole
chosen
Indicates the specific function or responsibility an entity has within a rail network system.
-
B.
railwayLineRole
Indicates the specific functional role or purpose that a railway line serves within a rail network or transportation system.
-
C.
railwayTrafficRole
Indicates the specific function or responsibility an entity has within the operation, management, or control of railway traffic.
-
D.
railwayNetworkSector
Indicates a relationship where something is classified as, or associated with, a specific sector or segment of a railway network.
-
E.
belongsToRailNetwork
Indicates that something is part of, or included within, a specific rail network.
- 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ed6fe888190b553ba6879cb2d8d |
completed | April 20, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:38 p.m.