Triple

T34902093
Position Surface form Disambiguated ID Type / Status
Subject Shoranur E1006617 entity
Predicate isKeyRailHubFor P523 FINISHED
Object Central Kerala 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: Central Kerala | Statement: [Shoranur, isKeyRailHubFor, Central Kerala]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isKeyRailHubFor
Context triple: [Shoranur, isKeyRailHubFor, Central Kerala]
  • A. isRailHubFor chosen
    Indicates that a location functions as a central node or interchange point within a rail network for the referenced area, routes, or services.
  • B. isKeyTransportHubIn
    Indicates that a location functions as a primary node for transporting people or goods within the specified area or network.
  • C. isTransportHubType
    Indicates that something serves as or belongs to a particular category of transport hub (such as a station, port, or terminal).
  • D. isKeyTransitHub
    Indicates that a location functions as a major transfer point where multiple transportation routes or modes intersect and a high volume of passenger or cargo movement is concentrated.
  • E. isRegionalHubOn
    Indicates that an entity functions as a primary regional hub or central node located on or served by a specified network, route, or infrastructure.
  • 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_69f76dc1b4a081909b4c6e4d8ec0aa2d completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f782c98fa08190870b68de2c1ff26a completed May 3, 2026, 5:15 p.m.
PD Predicate disambiguation batch_69f781020cc4819088c40cb8589504e4 completed May 3, 2026, 5:08 p.m.
Created at: May 3, 2026, 4 p.m.