Triple

T20690949
Position Surface form Disambiguated ID Type / Status
Subject Lami E508546 entity
Predicate languageUsed P238 FINISHED
Object Fiji Hindi 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: Fiji Hindi | Statement: [Lami, languageUsed, Fiji Hindi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fiji Hindi
Context triple: [Lami, languageUsed, Fiji Hindi]
  • A. Fiji Hindi chosen
    Fiji Hindi is an Indo-Aryan language spoken primarily by the Indo-Fijian community in Fiji, developed from dialects of North Indian languages brought by indentured laborers and influenced by English and Fijian.
  • B. Hindiyah
    Hindiyah is a town in Iraq, located in the Babil Governorate, known as the birthplace of former Prime Minister Nouri al-Maliki.
  • C. Andaman Hindi
    Andaman Hindi is a regional variety of Hindi that serves as a lingua franca among diverse communities in the Andaman Islands, including Great Andamanese speakers.
  • D. Hindko
    Hindko is a group of Indo-Aryan dialects spoken primarily in northern Pakistan, especially in parts of Khyber Pakhtunkhwa and Azad Kashmir.
  • E. Juang Bhasha
    Juang Bhasha is an endangered Munda language spoken by the Juang indigenous community in eastern India, primarily in the state of Odisha.
  • 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_69e0b4c1ed408190b72dd26b1e33f8a1 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6c10d83548190a52b9ef84c8f9205 completed April 21, 2026, 12:13 a.m.
Created at: April 16, 2026, 12:08 p.m.