Triple

T9851986
Position Surface form Disambiguated ID Type / Status
Subject Rromani E239489 entity
Predicate hasRelatedEthnicGroup P1969 FINISHED
Object Banjara E531896 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: Banjara | Statement: [Rromani, hasRelatedEthnicGroup, Banjara]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Banjara
Context triple: [Rromani, hasRelatedEthnicGroup, Banjara]
  • A. Banjara chosen
    Banjara are a traditionally nomadic tribal community of India known for their vibrant attire, folk traditions, and history as traders and transporters.
  • B. Badnera
    Badnera is a legislative assembly constituency in the Amravati district of Maharashtra, India.
  • C. Bhabra
    Bhabra is a town in the Alirajpur district of Madhya Pradesh, India, known as the birthplace of Indian revolutionary Chandra Shekhar Azad.
  • D. Pilibanga
    Pilibanga is a town in the Hanumangarh district of Rajasthan, India, known for its agricultural markets and proximity to the archaeological site of Kalibangan.
  • E. Tundla
    Tundla is a town in the Indian state of Uttar Pradesh known primarily as a major railway junction and transit hub in the Braj cultural region.
  • 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_69ca84e4fdc08190a624425bcef98665 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdb375ba448190a32cca2b0f376ac1 completed April 2, 2026, 12:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1d5ee190c8190957451d8d8291df3 completed April 5, 2026, 3:24 a.m.
Created at: March 30, 2026, 8:34 p.m.