Triple

T10594763
Position Surface form Disambiguated ID Type / Status
Subject Vemulavada Chalukya E250080 entity
Predicate capital P234 FINISHED
Object Vemulavada E865764 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: Vemulavada | Statement: [Vemulavada Chalukya, capital, Vemulavada]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vemulavada
Context triple: [Vemulavada Chalukya, capital, Vemulavada]
  • A. Vemulavada chosen
    Vemulavada is a historic town in present-day Telangana, India, known for its medieval temple heritage and prominence under the Vemulavada Chalukya dynasty.
  • B. Veeragase
    Veeragase is a vigorous and ritualistic folk dance-drama of Karnataka, India, traditionally performed during festivals to depict stories of valor from Hindu mythology.
  • C. Kadaru
    Kadaru is a Nubian language spoken by the Kadaru people in parts of Sudan.
  • D. Voruvoru
    Voruvoru is a small village located on Choiseul Island in the Solomon Islands, known for its rural setting and traditional Melanesian community.
  • E. Vanchi
    Vanchi was an ancient South Indian city that served as the political and cultural center of the Chera dynasty.
  • 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_69d381c9d3d48190a29ee491e1696a0e completed April 6, 2026, 9:50 a.m.
NER Named-entity recognition batch_69d5278cbf9081909ef419b0144d5019 completed April 7, 2026, 3:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69d95e8de2e88190835954abb2ac2ece completed April 10, 2026, 8:33 p.m.
Created at: April 6, 2026, 12:41 p.m.