Triple

T3137892
Position Surface form Disambiguated ID Type / Status
Subject Bundelkhand Expressway E65576 entity
Predicate connectsRegionTo P24718 FINISHED
Object key economic centers in Uttar Pradesh 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: key economic centers in Uttar Pradesh | Statement: [Bundelkhand Expressway, connectsRegionTo, key economic centers in Uttar Pradesh]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: connectsRegionTo
Context triple: [Bundelkhand Expressway, connectsRegionTo, key economic centers in Uttar Pradesh]
  • A. connectsRegions chosen
    Indicates a relationship where one entity links or joins two or more distinct regions, enabling passage, interaction, or continuity between them.
  • B. linkedToRegion
    Indicates that one entity is associated or connected to a specific geographic or administrative region.
  • C. connectsArea
    Indicates that one area serves as a link or passage between two other areas, enabling movement or interaction between them.
  • D. connectsTo
    Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
  • E. connectsViaCanal
    Indicates that one entity is linked or joined to another by means of a canal.
  • 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_69ad8581c25c8190b0d85ba9b9baa531 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada574509c81908a88bb10ea35516d completed March 8, 2026, 4:36 p.m.
PD Predicate disambiguation batch_69ad9df840088190a26a1516f4c1f056 completed March 8, 2026, 4:04 p.m.
Created at: March 8, 2026, 3:05 p.m.