Triple
T38030119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dausa railway station |
E948884
|
entity |
| Predicate | locatedOnHighwayCorridor |
—
|
GENERATED |
| Object | Delhi–Jaipur corridor |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnHighwayCorridor Context triple: [Dausa railway station, locatedOnHighwayCorridor, Delhi–Jaipur corridor]
-
A.
isLocatedOnHighway
Indicates that one entity is situated along, adjacent to, or directly accessible from a specific highway.
-
B.
locatedInTransportCorridor
chosen
Indicates that an entity is situated within a designated transport corridor used for the movement of people or goods.
-
C.
roadCorridorIncludes
Indicates that a specified road corridor spatially contains or encompasses another element or segment within its defined bounds.
-
D.
positionOnHighway
Indicates that one entity’s location is specified relative to a particular highway, such as being on, along, or at a point on that highway.
-
E.
connectsToHighway
Indicates that one location, road, or route has a direct access point or linkage to a highway.
- F. None of above.
Provenance (1 batch)
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_69f76efd1bc48190a729097fe5177b61 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.