Triple
T38030119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dausa railway station |
E948884
|
entity |
| Predicate | locatedOnHighwayCorridor |
P86239
|
FINISHED |
| Object | Delhi–Jaipur corridor |
E381351
|
NE 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: Delhi–Jaipur corridor | Statement: [Dausa railway station, locatedOnHighwayCorridor, Delhi–Jaipur corridor]
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 (4 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_69f76efd1bc48190a729097fe5177b61 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4154432b1481909a2edee90ccd8d3b |
completed | June 28, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.