Triple
T36313236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kazipet |
E894117
|
entity |
| Predicate | isRailwayHubOf |
P170780
|
FINISHED |
| Object | northern Telangana |
—
|
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: northern Telangana | Statement: [Kazipet, isRailwayHubOf, northern Telangana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRailwayHubOf Context triple: [Kazipet, isRailwayHubOf, northern Telangana]
-
A.
isRegionalRailwayHub
chosen
Indicates that a location functions as a central node in a regional railway network, where multiple rail lines converge or are coordinated.
-
B.
hasRailwayStationOn
Indicates that a railway station is located on or serves a particular railway line, route, or network segment.
-
C.
isTransportCenterOf
Indicates that a location functions as a primary hub or central node for transportation activities serving another area or network.
-
D.
railwayConnectsTo
Indicates that one railway line, track, or network is directly linked or joined to another, allowing trains to move between them.
-
E.
isCapitalCityStationOf
Indicates that a particular station serves as the main or primary railway/transport station of a capital city.
- 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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.