Triple

T19381200
Position Surface form Disambiguated ID Type / Status
Subject Kota railway division E484814 entity
Predicate divisionCode P30519 FINISHED
Object KOTA 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: KOTA | Statement: [Kota railway division, divisionCode, KOTA]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: KOTA
Context triple: [Kota railway division, divisionCode, KOTA]
  • A. KOTA
    KOTA is a Timorese political party that participated in the resistance movement against Indonesian occupation and later in East Timor’s post-independence politics.
  • B. Kota chosen
    Kota is a major industrial and educational city in southeastern Rajasthan, India, known for its coaching institutes and power plants along the Chambal River.
  • C. Kokota
    Kokota is an Oceanic language spoken in the Solomon Islands, particularly on Santa Isabel Island.
  • D. Kota Ukir
    Kota Ukir is a nickname for Jepara, an Indonesian town renowned for its intricate woodcarving and furniture craftsmanship.
  • E. Kota Patriot
    Kota Patriot is a popular nickname for the Indonesian city of Bekasi, reflecting its historical and patriotic identity.
  • 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_69d8e8d460d88190abf0591c5c9d2b0c completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e61a6075a88190aed7afa3b8fd3021 completed April 20, 2026, 12:21 p.m.
Created at: April 10, 2026, 1:35 p.m.