Triple

T11988973
Position Surface form Disambiguated ID Type / Status
Subject Koli community E285354 entity
Predicate hasSubgroup P747 FINISHED
Object Son Koli E639677 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: Son Koli | Statement: [Koli community, hasSubgroup, Son Koli]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Son Koli
Context triple: [Koli community, hasSubgroup, Son Koli]
  • A. Son Koli chosen
    Son Koli is a subcaste of the Koli community in India, traditionally associated with fishing and coastal livelihoods, particularly in the western coastal regions such as Maharashtra.
  • B. Koliyas
    Koliyas was an ancient republican clan in northern India, historically known as a neighboring polity to the Shakya tribe during the time of the Buddha.
  • C. Kolahun
    Kolahun is a town in northwestern Liberia that serves as one of the main local centers of administration and commerce in Lofa County.
  • D. Sarikoli
    Sarikoli is an Eastern Iranian language spoken primarily by the Tajik ethnic community in the Tashkurgan region of Xinjiang, China.
  • E. Dhor Koli
    Dhor Koli is a subcaste within the broader Koli community of India, traditionally associated with fishing and other water-related occupations.
  • 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_69d6ab44a77c8190a652f4b27164e4ef completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d903ae28708190a826bad1624343eb completed April 10, 2026, 2:05 p.m.
NED1 Entity disambiguation (via context triple) batch_69f472492ebc8190b064e691bb70e356 completed May 1, 2026, 9:28 a.m.
Created at: April 8, 2026, 9:46 p.m.