Triple

T23395347
Position Surface form Disambiguated ID Type / Status
Subject Berar region E559341 entity
Predicate historicalName P65 FINISHED
Object Berar 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: Berar | Statement: [Berar region, historicalName, Berar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Berar
Context triple: [Berar region, historicalName, Berar]
  • A. Berar chosen
    Berar was a historical region in central India that became a significant Maratha-ruled province, later integrated into British India and now largely part of Maharashtra.
  • B. Bjerka
    Bjerka is a small village in the municipality of Hemnes in Nordland county, Norway.
  • C. Bergharen
    Bergharen is a village in the Dutch province of Gelderland, known for its historic church and rural surroundings.
  • D. Bytnar
    Bytnar is a Polish surname most notably associated with Jan Bytnar, a young resistance fighter and national hero during World War II.
  • E. Bereina
    Bereina is a small town in Papua New Guinea’s Central Province, known primarily as a rural administrative and service center for surrounding villages.
  • 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_69e24549610c8190a069d6411ce5f661 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1a4db1c888190ace5d58bcc8645c1 completed April 29, 2026, 6:27 a.m.
Created at: April 17, 2026, 5:36 p.m.