Triple

T19785985
Position Surface form Disambiguated ID Type / Status
Subject Chilla (near Banda, Uttar Pradesh) E475266 entity
Predicate locatedNear P294 FINISHED
Object Banda 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: Banda | Statement: [Chilla (near Banda, Uttar Pradesh), locatedNear, Banda]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Banda
Context triple: [Chilla (near Banda, Uttar Pradesh), locatedNear, Banda]
  • A. Banda chosen
    Banda is a city in the Bundelkhand region of Uttar Pradesh, India, known for its historical significance and proximity to the Ken River.
  • B. Banda
    Banda is a town in the Sagar district of the central Indian state of Madhya Pradesh.
  • C. Banda Arc
    The Banda Arc is a complex volcanic island arc and tectonic boundary in eastern Indonesia, formed by the collision and subduction of multiple tectonic plates around the Banda Sea.
  • D. Banda-Linda
    Banda-Linda is a dialect of the Central Banda language spoken by the Banda people in parts of Central Africa, particularly in the Central African Republic.
  • E. Banda Besar
    Banda Besar is one of the main volcanic islands in Indonesia’s Banda Sea, known historically as part of the nutmeg-producing Banda Islands.
  • 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_69d8e51b014081908b263e167370529a completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e65387d3348190a31f9c2f9bc1c6d9 completed April 20, 2026, 4:25 p.m.
Created at: April 10, 2026, 1:49 p.m.