Triple

T729509
Position Surface form Disambiguated ID Type / Status
Subject Bal Gangadhar Tilak E14800 entity
Predicate birthPlace P1 FINISHED
Object Ratnagiri E79536 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: Ratnagiri | Statement: [Bal Gangadhar Tilak, birthPlace, Ratnagiri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ratnagiri
Context triple: [Bal Gangadhar Tilak, birthPlace, Ratnagiri]
  • A. Ratnagiri chosen
    Ratnagiri is a coastal city in Maharashtra, India, known for its Alphonso mangoes, historic forts, and scenic beaches along the Konkan coast.
  • B. Baramati
    Baramati is a town in the Pune district of Maharashtra, India, known as an agricultural and industrial hub with historical and political significance.
  • C. Sangli
    Sangli is a city in the Indian state of Maharashtra known for its fertile agricultural surroundings and prominence in sugar and turmeric production.
  • D. Sindhudurg
    Sindhudurg is a coastal district in Maharashtra, India, renowned for its historic sea fort, beaches, and scenic Konkan landscape.
  • E. Nanded
    Nanded is a historic city in the Indian state of Maharashtra, known as an important Sikh pilgrimage center and a major urban hub in the Marathwada region.
  • 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_69a4934d9930819099eed80096b0597d completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a5c290e481908497430a05dbfb90 completed March 1, 2026, 8:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69a64a5c9d248190b0bebfd0e999643a completed March 3, 2026, 2:41 a.m.
Created at: March 1, 2026, 7:37 p.m.