Triple

T8921797
Position Surface form Disambiguated ID Type / Status
Subject Karanja taluka E212436 entity
Predicate administrativeCentre P1474 FINISHED
Object Karanja E212429 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: Karanja | Statement: [Karanja taluka, administrativeCentre, Karanja]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Karanja
Context triple: [Karanja taluka, administrativeCentre, Karanja]
  • A. Karanja (Ghadge) chosen
    Karanja (Ghadge) is a town in Maharashtra, India, known as a local administrative and commercial center within the Wardha district.
  • B. Fagara
    Fagara is a genus of flowering plants in the citrus family Rutaceae, known for species that often have aromatic properties and spiny stems.
  • C. Bagassa
    Bagassa is a small genus of tropical trees in the mulberry family, known for species such as Bagassa guianensis found in South American rainforests.
  • D. Khaya
    Khaya is a genus of tropical African trees in the mahogany family, valued for their high-quality timber.
  • E. Guaiúba
    Guaiúba is a municipality in the state of Ceará, Brazil, located in the metropolitan region of Fortaleza.
  • 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_69ca839481d48190b42b037e0d0f636c completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc665024f081909515e02e5f5b2221 completed April 1, 2026, 12:26 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfba4f094c81909a30d3be640ac9e0 completed April 3, 2026, 1:02 p.m.
Created at: March 30, 2026, 6:56 p.m.