Triple

T5844922
Position Surface form Disambiguated ID Type / Status
Subject Baghelkhand E129684 entity
Predicate historicalCapital P2536 FINISHED
Object Rewa E110278 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: Rewa | Statement: [Baghelkhand, historicalCapital, Rewa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rewa
Context triple: [Baghelkhand, historicalCapital, Rewa]
  • A. Rewa
    Rewa is an alternative name for the Narmada River, one of central India's major and holiest rivers.
  • B. Rewa chosen
    Rewa is a prominent city in northeastern Madhya Pradesh, India, known historically as the seat of the former Rewa princely state and for its cultural and administrative significance in the region.
  • C. Rewa
    Rewa is a coastal village in northern Poland situated along the Baltic Sea, known for its sandy beaches and popular windsurfing and kitesurfing conditions.
  • D. Kareli
    Kareli is a town in central Georgia that serves as an important local center within the Shida Kartli region.
  • E. Umaria
    Umaria is a town and district headquarters in the central Indian state of Madhya Pradesh, known as a gateway to the nearby Bandhavgarh National Park.
  • 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_69c0084bd31c8190a796bb6284845e83 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c034dcafe88190a438034a539ffa52 completed March 22, 2026, 6:28 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0a1a9ffa881908b38eeddb411c4ab completed March 23, 2026, 2:12 a.m.
Created at: March 22, 2026, 3:55 p.m.