Triple

T14937908
Position Surface form Disambiguated ID Type / Status
Subject Mandvi E372443 entity
Predicate administrativeDivision P747 FINISHED
Object Mandvi Taluka E955932 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: Mandvi Taluka | Statement: [Mandvi, administrativeDivision, Mandvi Taluka]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mandvi Taluka
Context triple: [Mandvi, administrativeDivision, Mandvi Taluka]
  • A. Mandvi taluka chosen
    Mandvi taluka is an administrative subdivision (taluka) within Surat district in the state of Gujarat, India.
  • B. Bhuj taluka
    Bhuj taluka is an administrative subdivision in the Kutch district of Gujarat, India, encompassing the town of Bhuj and surrounding villages in the region.
  • C. Vengurla taluka
    Vengurla taluka is an administrative subdivision in the coastal Sindhudurg district of Maharashtra, India, known for its beaches, temples, and historic trading port.
  • D. Shrivardhan taluka
    Shrivardhan taluka is an administrative subdivision in Maharashtra, India, centered around the coastal town of Shrivardhan and known for its beaches and historical significance.
  • E. Mangrol taluka
    Mangrol taluka is an administrative subdivision (taluka) within Surat district in the state of Gujarat, India.
  • 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_69d85cc9da0c81908d583ca3f63a3908 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded64904d88190b6b4140da8e8199d completed April 15, 2026, 12:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe7e8e9c0c81909cfb1e02987527c0 completed May 9, 2026, 12:23 a.m.
Created at: April 10, 2026, 2:38 a.m.