Triple

T16528601
Position Surface form Disambiguated ID Type / Status
Subject Pune IT corridor E401502 entity
Predicate cityRankWithinIndiaByIT P123896 FINISHED
Object one of the leading IT hubs in India 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: one of the leading IT hubs in India | Statement: [Pune IT corridor, cityRankWithinIndiaByIT, one of the leading IT hubs in India]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: cityRankWithinIndiaByIT
Context triple: [Pune IT corridor, cityRankWithinIndiaByIT, one of the leading IT hubs in India]
  • A. areaRankInIndia
    Indicates the relative position of an entity when all entities in India are ordered by their area size.
  • B. rankByPopulationInIndia
    Indicates the relative ordering of entities based on their population size within India.
  • C. populationRankInTelangana
    Indicates the relative position of an entity in terms of population size compared to other entities within Telangana.
  • D. populationRankInWestBengal
    Indicates the relative position of an entity in terms of population size compared to other entities within West Bengal.
  • E. rankByLengthInIndia
    Indicates an ordering of items based on their length specifically within the context or boundaries of India.
  • F. None of above. chosen

Provenance (4 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_69d883838abc8190bc79cb2d41733ce2 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e32ed57be481908625d4c5aab0940c completed April 18, 2026, 7:12 a.m.
PD Predicate disambiguation batch_69e296995d388190b88ebe189dce890d completed April 17, 2026, 8:22 p.m.
PDg Predicate description generation batch_69e2d7f97e548190a474691a152bd8e8 completed April 18, 2026, 1:01 a.m.
Created at: April 10, 2026, 5:14 a.m.