Triple

T13223151
Position Surface form Disambiguated ID Type / Status
Subject Kankavli E314804 entity
Predicate hasNearbyTown P3883 FINISHED
Object Malvan E311540 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: Malvan | Statement: [Kankavli, hasNearbyTown, Malvan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Malvan
Context triple: [Kankavli, hasNearbyTown, Malvan]
  • A. Malvan chosen
    Malvan is a coastal town in Maharashtra, India, known for its beaches, seafood cuisine, and historic Sindhudurg Fort.
  • B. Mehsana
    Mehsana is a prominent city in the Indian state of Gujarat, known for its dairy industry, oil and natural gas fields, and historical temples.
  • C. Aonla
    Aonla is a parliamentary constituency in Uttar Pradesh, India, known for its agricultural economy and political significance.
  • D. Malvani
    Malvani is an Indo-Aryan language variety spoken primarily in the Konkan coastal region of Maharashtra and Goa, closely related to Marathi and Konkani.
  • E. Santal
    Santal are an indigenous ethnic group of South Asia, primarily found in India, Bangladesh, and Nepal, known for their distinct Austroasiatic language, rich oral traditions, and agrarian lifestyle.
  • 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_69d806affc688190a25b6ccc588e9c72 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98cf74d708190a61d8ad938653b06 completed April 10, 2026, 11:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69f70a3407388190bef886884cb75912 completed May 3, 2026, 8:41 a.m.
Created at: April 9, 2026, 9:19 p.m.