Triple
T24801028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ranjangaon, Maharashtra, India |
E620521
|
entity |
| Predicate | nearestRailwayHub |
P82238
|
FINISHED |
| Object | Pune Junction |
—
|
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: Pune Junction | Statement: [Ranjangaon, Maharashtra, India, nearestRailwayHub, Pune Junction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestRailwayHub Context triple: [Ranjangaon, Maharashtra, India, nearestRailwayHub, Pune Junction]
-
A.
nearestRailwayTerminus
Indicates that one location is the closest railway terminus to another specified place.
-
B.
nearestPassengerRailStation
Indicates that one entity is the closest passenger rail station in distance to another entity.
-
C.
nearestMajorRailwayJunction
chosen
Indicates the closest significant railway junction in terms of distance from a given location or entity.
-
D.
nearestSuburbanRailwayStation
Indicates the relationship where a given place is associated with the suburban railway station that is geographically closest to it.
-
E.
nearestRailwayLine
Indicates that one railway line is the closest in distance to a given location or feature compared to all other railway lines.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 4:49 a.m.