Triple

T32664360
Position Surface form Disambiguated ID Type / Status
Subject Noida Link Road E835116 entity
Predicate connectsAdministrativeAreas P87027 FINISHED
Object Delhi 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: Delhi | Statement: [Noida Link Road, connectsAdministrativeAreas, Delhi]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: connectsAdministrativeAreas
Context triple: [Noida Link Road, connectsAdministrativeAreas, Delhi]
  • A. connectsAdministrativeArea chosen
    Indicates a relationship where one entity serves as a link or route between two administrative areas (such as regions, districts, or municipalities).
  • B. mapsToAdministrativeAreas
    Indicates that something is associated with, assigned to, or corresponds to one or more defined administrative areas or regions.
  • C. administrativeDistricts
    Indicates that one entity serves as an administrative district or subdivision governed or managed by another entity.
  • D. hasAdministrativeArea
    Indicates that one entity serves as the governing or jurisdictional area responsible for administering another entity.
  • E. administrativeTerritorialEntityOf
    Indicates that one entity serves as the administrative territorial unit or jurisdiction to which another entity belongs or is governed by.
  • 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_69f349303ccc8190a70d0f6e8a21d3fb completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69feecf1bb248190ba30f0bb1d22ee08 completed May 9, 2026, 8:14 a.m.
PD Predicate disambiguation batch_69feea5f27748190b223ee4e3ba5a678 completed May 9, 2026, 8:03 a.m.
Created at: May 1, 2026, 1:08 a.m.