Triple

T9704715
Position Surface form Disambiguated ID Type / Status
Subject Nashik district E234869 entity
Predicate containsTown P847 FINISHED
Object Yeola E128969 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: Yeola | Statement: [Nashik district, containsTown, Yeola]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yeola
Context triple: [Nashik district, containsTown, Yeola]
  • A. Yeola chosen
    Yeola is a town in the Nashik district of Maharashtra, India, known historically as the birthplace of the Indian freedom fighter Tatya Tope.
  • B. Eliada
    Eliada is a lesser-known biblical figure mentioned in the Old Testament as one of King David’s sons.
  • C. Tynaarlo
    Tynaarlo is a municipality in the northeastern Netherlands known for its rural character and location between the cities of Groningen and Assen.
  • D. Modara
    Modara is a coastal urban neighborhood in Colombo, Sri Lanka, known for its port-adjacent location and dense residential and commercial activity.
  • E. Palena
    Palena is a small town and municipality in the Palena Province of Chile’s Los Lagos Region, known for its remote Andean landscapes and outdoor tourism.
  • 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_69ca84cc78808190a56f3402b7c139a7 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9d74afb4819084174aab5bcdb6e0 completed April 1, 2026, 10:34 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1af93b76c81908377f17956fb86b1 completed April 5, 2026, 12:40 a.m.
Created at: March 30, 2026, 8:18 p.m.