Triple

T4823207
Position Surface form Disambiguated ID Type / Status
Subject Radha E107758 entity
Predicate associatedPlace P1481 FINISHED
Object Nandgaon E305241 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: Nandgaon | Statement: [Radha, associatedPlace, Nandgaon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nandgaon
Context triple: [Radha, associatedPlace, Nandgaon]
  • A. Nandgaon chosen
    Nandgaon is a historic town in the Braj region of India, revered in Hindu tradition as the childhood home of Lord Krishna and an important pilgrimage site.
  • B. Nandod
    Nandod is the former name of the town now known as Rajpipla in the Indian state of Gujarat.
  • C. Sawantwadi
    Sawantwadi is a historic town in Maharashtra, India, known for its former royal palace, traditional wooden toys, and scenic location near the Goa border.
  • D. Baramati
    Baramati is a town in the Pune district of Maharashtra, India, known as an agricultural and industrial hub with historical and political significance.
  • E. Lohegaon
    Lohegaon is a suburban area of Pune, India, known for its residential neighborhoods and proximity to key transport and defense installations.
  • 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_69bd43f9efa081908314cb3e94fa1695 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6cac2bd08190b3f7cfe691fed052 completed March 20, 2026, 3:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69be4dc6ddcc8190903c0737476bbe36 completed March 21, 2026, 7:50 a.m.
Created at: March 20, 2026, 1:24 p.m.