Triple

T23395458
Position Surface form Disambiguated ID Type / Status
Subject Jalgaon division (informal) E559344 entity
Predicate hasMajorTown P316 FINISHED
Object Amalner 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: Amalner | Statement: [Jalgaon division (informal), hasMajorTown, Amalner]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Amalner
Context triple: [Jalgaon division (informal), hasMajorTown, Amalner]
  • A. Amalner chosen
    Amalner is a town in the Indian state of Maharashtra known for its textile industry and as the birthplace of the Wipro company.
  • B. Kharadi
    Kharadi is a rapidly developing suburb in Pune, India, known as a major IT and business hub with modern infrastructure and residential complexes.
  • C. Bhoranj
    Bhoranj is a town in the Hamirpur district of Himachal Pradesh, India, known as a local administrative and commercial center for surrounding rural areas.
  • D. Parbhani
    Parbhani is a significant city in the Marathwada region of Maharashtra, India, known as an important commercial and educational center.
  • E. Karmala
    Karmala is a town in Maharashtra, India, known as a local administrative and commercial center within Solapur district.
  • 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_69e24549610c8190a069d6411ce5f661 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1a4db1c888190ace5d58bcc8645c1 completed April 29, 2026, 6:27 a.m.
Created at: April 17, 2026, 5:36 p.m.