Triple
T38317004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delhi Jn |
E1033852
|
entity |
| Predicate | majorRoutes |
P141455
|
FINISHED |
| Object | Delhi–Howrah main line |
—
|
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: Delhi–Howrah main line | Statement: [Delhi Jn, majorRoutes, Delhi–Howrah main line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorRoutes Context triple: [Delhi Jn, majorRoutes, Delhi–Howrah main line]
-
A.
majorRouteTo
Indicates that one location serves as a primary or significant route or pathway leading to another location.
-
B.
firstMajorRoute
Indicates that the specified route is the primary or earliest major route associated with an entity (such as a location, project, or network).
-
C.
primaryRoutes
chosen
Indicates the main or most important routes that connect or serve between specified locations or entities.
-
D.
mainRoadInfrastructure
Indicates that a road segment functions as a primary or major route within the transportation infrastructure network.
-
E.
isMajorTrafficRoute
Indicates that a road or pathway serves as a primary, heavily used route for traffic flow within a transportation network.
- 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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a004a8892c08190bcacb952ad737716 |
completed | May 10, 2026, 9:06 a.m. |
| PD | Predicate disambiguation | batch_6a004a44b4948190be4b3dbfce8da020 |
completed | May 10, 2026, 9:05 a.m. |
Created at: May 3, 2026, 4:30 p.m.