Triple
T32976878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kharagpur–Puri line |
E843688
|
entity |
| Predicate | connectsToMainJunction |
P35426
|
FINISHED |
| Object | Howrah Junction via Kharagpur |
—
|
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: Howrah Junction via Kharagpur | Statement: [Kharagpur–Puri line, connectsToMainJunction, Howrah Junction via Kharagpur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsToMainJunction Context triple: [Kharagpur–Puri line, connectsToMainJunction, Howrah Junction via Kharagpur]
-
A.
connectsToMainLineAt
chosen
Indicates that one entity is linked or joined to a primary or central line at a specific point.
-
B.
servesJunction
Indicates that one element functions as a connecting or branching point where multiple other elements meet or intersect.
-
C.
isMajorRoadJunction
Indicates that a location serves as a primary intersection where major roads or highways meet or cross.
-
D.
isNumberedJunctionOf
Indicates that a junction (such as a road or rail intersection) has been assigned an official identifying number within a network.
-
E.
hasRoadJunctionType
Indicates that a road junction has a specific type or classification (e.g., roundabout, intersection, interchange).
- 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_69f3494b9fc48190bb61c955ba471275 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
Created at: May 1, 2026, 1:22 a.m.