Triple

T19118632
Position Surface form Disambiguated ID Type / Status
Subject Saurashtra–Kutch E467976 entity
Predicate hasMajorPort P942 FINISHED
Object Kandla 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: Kandla | Statement: [Saurashtra–Kutch, hasMajorPort, Kandla]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kandla
Context triple: [Saurashtra–Kutch, hasMajorPort, Kandla]
  • A. Kandla chosen
    Kandla is a major port city in the state of Gujarat, India, known for its significant role in maritime trade and logistics.
  • B. Jamnagar
    Jamnagar is a city in the Indian state of Gujarat, known for its oil refineries, brass industries, and proximity to the Gulf of Kutch.
  • C. Gandhidham
    Gandhidham is a planned town in the Kutch district of Gujarat, India, developed primarily to resettle refugees after the Partition and serving as a key commercial hub in the region.
  • D. Surendranagar
    Surendranagar is a city in the Indian state of Gujarat known historically as a regional trade and administrative center.
  • E. Khambhat
    Khambhat is a historic coastal town in Gujarat, India, known for its ancient port, trade heritage, and distinctive gulf on the Arabian Sea.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8dd06a26481908039e2a1bae8c597 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5e3c756a88190942930e6ae7242a7 completed April 20, 2026, 8:28 a.m.
Created at: April 10, 2026, 12:05 p.m.