Triple

T17409417
Position Surface form Disambiguated ID Type / Status
Subject Hirabai Daboo E423306 entity
Predicate spouseBirthPlace P100541 FINISHED
Object Navsari 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: Navsari | Statement: [Hirabai Daboo, spouseBirthPlace, Navsari]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Navsari
Context triple: [Hirabai Daboo, spouseBirthPlace, Navsari]
  • A. Navsari chosen
    Navsari is a city in the Indian state of Gujarat known historically as a center of Parsi culture and commerce.
  • B. Naupada
    Naupada is a prominent residential and commercial locality within the city of Thane in Maharashtra, India.
  • C. Marvadi
    Marvadi is an alternative name for the Marwari people and their Indo-Aryan language traditionally associated with the Marwar region of Rajasthan, India.
  • D. Veraval
    Veraval is a coastal city in the Indian state of Gujarat, known historically as a major fishing and port town near the pilgrimage center of Somnath.
  • E. Navalgund
    Navalgund is a town in the Indian state of Karnataka known for its traditional handloom cotton and silk sarees, especially the distinctive Navalgund durries.
  • 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_69d889d7d27c819088486ce3f0627fa1 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43b0990f48190b62d73087ae1a0d7 completed April 19, 2026, 2:16 a.m.
Created at: April 10, 2026, 5:46 a.m.