Triple
T35572411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kudal railway station |
E1027974
|
entity |
| Predicate | stateRailwayNetwork |
P24517
|
FINISHED |
| Object | Maharashtra rail network |
—
|
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: Maharashtra rail network | Statement: [Kudal railway station, stateRailwayNetwork, Maharashtra rail network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateRailwayNetwork Context triple: [Kudal railway station, stateRailwayNetwork, Maharashtra rail network]
-
A.
railroadNetwork
chosen
Indicates a relationship where locations are connected as part of the same system of railway lines and infrastructure used for train transport.
-
B.
railwayCompanyNetwork
Indicates a relationship where a railway company operates, manages, or is responsible for a particular rail network or system.
-
C.
railNetworkCenter
Indicates that a location functions as a central hub or focal point within a rail transportation network.
-
D.
hasRailSystem
Indicates that an entity possesses or is served by a rail-based transportation system.
-
E.
railNetworkCountry
Indicates that a rail network is located within, or primarily serves, a specific country.
- 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_69f76e0386688190b931bacdc145938c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fec25f0fc48190b87ab1f9cd1eb0de |
completed | May 9, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69fec079a770819098df7cc3049df954 |
completed | May 9, 2026, 5:04 a.m. |
Created at: May 3, 2026, 4:04 p.m.