Triple
T29948195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Igatpuri |
E760695
|
entity |
| Predicate | isKeyRailStopOnRouteBetween |
P128427
|
FINISHED |
| Object | Mumbai and central India |
—
|
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: Mumbai and central India | Statement: [Igatpuri, isKeyRailStopOnRouteBetween, Mumbai and central India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeyRailStopOnRouteBetween Context triple: [Igatpuri, isKeyRailStopOnRouteBetween, Mumbai and central India]
-
A.
isBetweenStationsOnLine
Indicates that something is located or occurs between two stations along the same transit line.
-
B.
railNetworkStopOn
Indicates that a rail stop or station is located on and served by a particular rail network.
-
C.
hasRailRoute
Indicates that there exists a rail-based transportation route or connection between the related entities.
-
D.
isTransitPointOn
chosen
Indicates that one location serves as an intermediate transit point along a specified route, path, or journey.
-
E.
isRailwayIn
Indicates that a railway is located within or passes through a specified geographic or administrative 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 6:24 p.m.