Triple
T26153629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chakdaha |
E659894
|
entity |
| Predicate | isOnRailwayDivision |
P1921
|
FINISHED |
| Object | Sealdah railway division |
—
|
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: Sealdah railway division | Statement: [Chakdaha, isOnRailwayDivision, Sealdah railway division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnRailwayDivision Context triple: [Chakdaha, isOnRailwayDivision, Sealdah railway division]
-
A.
railwayDivision
chosen
Indicates that one administrative railway division is responsible for, manages, or encompasses another railway unit, line, or area within a rail network.
-
B.
isOnRailway
Indicates that one entity is positioned on, aligned with, or traveling along a railway track or railway system in relation to another entity.
-
C.
railwayDivisionHeadquartersOf
Indicates that one location serves as the administrative headquarters for a specified railway division.
-
D.
isRailwayIn
Indicates that a railway is located within or passes through a specified geographic or administrative area.
-
E.
hasRailwayZone
Indicates that a location or railway entity falls under the jurisdiction or coverage area of a specific railway zone.
- 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_69ee5bc5a9908190899d39ce95c6d215 |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f60c0d35288190b016726366d3ad27 |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:26 p.m.