Triple

T6187808
Position Surface form Disambiguated ID Type / Status
Subject Dholera E138105 entity
Predicate transportPlanned P69563 FINISHED
Object expressway connectivity to Ahmedabad 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: expressway connectivity to Ahmedabad | Statement: [Dholera, transportPlanned, expressway connectivity to Ahmedabad]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: transportPlanned
Context triple: [Dholera, transportPlanned, expressway connectivity to Ahmedabad]
  • A. transportationPlanned
    Indicates that an arrangement has been made for someone or something to be transported from one place to another.
  • B. transportAdvisory
    Indicates that guidance, warnings, or recommendations are being issued regarding transportation conditions, operations, or usage.
  • C. transportIncludes
    Indicates that a broader transport operation or service encompasses, contains, or makes use of a specific transport segment, mode, or component as part of its overall movement.
  • D. travelPattern
    Indicates the typical routes, frequencies, and behaviors associated with how an entity moves or travels between locations.
  • E. transportCorridor
    Indicates a route or pathway used to move people, goods, or resources between locations.
  • 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_69c008a8fd408190b7ec6e42934974a6 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c06217be288190997032c8c4839fa5 completed March 22, 2026, 9:41 p.m.
PD Predicate disambiguation batch_69c055fa0a808190bda37832e3ac150c completed March 22, 2026, 8:50 p.m.
PDg Predicate description generation batch_69c056c87340819088003f427706ebf8 completed March 22, 2026, 8:53 p.m.
Created at: March 22, 2026, 4:19 p.m.