Triple

T19118633
Position Surface form Disambiguated ID Type / Status
Subject Saurashtra–Kutch E467976 entity
Predicate hasMajorPort P942 FINISHED
Object Mundra 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: Mundra | Statement: [Saurashtra–Kutch, hasMajorPort, Mundra]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mundra
Context triple: [Saurashtra–Kutch, hasMajorPort, Mundra]
  • A. Mundra chosen
    Mundra is a coastal town in the Kutch region of Gujarat, India, known today for its major port and industrial infrastructure.
  • B. Naupada
    Naupada is a prominent residential and commercial locality within the city of Thane in Maharashtra, India.
  • C. Mandvi
    Mandvi is a historic coastal town in Gujarat, India, known for its shipbuilding heritage, beaches, and trading history within the Kutch region.
  • D. Mazagaon
    Mazagaon is one of the original seven islands that historically merged to form the modern city of Mumbai, India.
  • E. Vengurla
    Vengurla is a coastal town in Maharashtra, India, known for its scenic beaches, historic forts, and cashew plantations.
  • 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.