Triple
T26400760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kharagpur Workshop |
E663689
|
entity |
| Predicate | servesRailwayZone |
P24188
|
FINISHED |
| Object | South Eastern Railway zone |
—
|
NE NERFINISHED |
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: South Eastern Railway zone | Statement: [Kharagpur Workshop, servesRailwayZone, South Eastern Railway zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesRailwayZone Context triple: [Kharagpur Workshop, servesRailwayZone, South Eastern Railway zone]
-
A.
hasRailwayZone
chosen
Indicates that a location or railway entity falls under the jurisdiction or coverage area of a specific railway zone.
-
B.
railwayZoneType
Indicates the classification or category of a railway zone to which a given railway-related entity belongs.
-
C.
servesRailCorridor
Indicates that something (such as a service, facility, or operation) provides service to or operates along a specific rail corridor.
-
D.
railwayTypeServed
Indicates the type of railway system or service that a given entity (such as a station, line, or facility) is designed to serve or accommodate.
-
E.
railwaySystemServed
Indicates that a railway system provides service to, or operates within, a specified location or area.
- 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 26, 2026, 11:31 p.m.