Triple

T16284087
Position Surface form Disambiguated ID Type / Status
Subject Ahmedabad–Vadodara line E395343 entity
Predicate connects P390 FINISHED
Object Vadodara E126802 NE 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: Vadodara | Statement: [Ahmedabad–Vadodara line, connects, Vadodara]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vadodara
Context triple: [Ahmedabad–Vadodara line, connects, Vadodara]
  • A. Vadodara chosen
    Vadodara is a major city in western India known for its rich cultural heritage, educational institutions, and industrial development.
  • B. Ahmedabad
    Ahmedabad is a major city in the western Indian state of Gujarat, known for its rich history, textile industry, and role as an important economic and cultural center.
  • C. Indore
    Indore is a major commercial and educational hub in central India, known for its vibrant markets, food culture, and rapidly growing urban infrastructure.
  • D. Bhavnagar
    Bhavnagar is a coastal city in western India known for its historic trading port, diamond cutting industry, and cultural heritage within the state of Gujarat.
  • E. Rajkot
    Rajkot is a major city in the Indian state of Gujarat, known as an important commercial and cultural center of the Saurashtra region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d87f22c7248190a54c949738441e2e completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e24912c5808190a0d9c9f491315068 completed April 17, 2026, 2:52 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0084a88dc08190a78973bc71f179d4 completed May 10, 2026, 1:14 p.m.
Created at: April 10, 2026, 5:05 a.m.