Triple

T19467836
Position Surface form Disambiguated ID Type / Status
Subject Kanabhuk E487045 entity
Predicate sameAs P6530 FINISHED
Object Uluka 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: Uluka | Statement: [Kanabhuk, sameAs, Uluka]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Uluka
Context triple: [Kanabhuk, sameAs, Uluka]
  • A. Uluka chosen
    Uluka is an alternative name for the Kannada language, a major Dravidian language spoken predominantly in the Indian state of Karnataka.
  • B. Iluka
    Iluka is a small coastal town in northern New South Wales, Australia, known for its beaches, fishing, and proximity to the Clarence River and Iluka Nature Reserve.
  • C. Wiluna
    Wiluna is a remote outback town in Western Australia known historically as a gold mining center and as a gateway to desert tracks such as the Canning Stock Route.
  • D. Maleka
    Maleka is a feminine given name, typically considered a variant spelling of Malika and used in various cultures.
  • E. Urakhi
    Urakhi is a dialect of the Dargin language spoken by a subset of the Dargin people in the North Caucasus region of Russia.
  • 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_69d8e8d86d608190bd199a98d0297f27 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e633e2aee081908330a5665fa60482 completed April 20, 2026, 2:10 p.m.
Created at: April 10, 2026, 1:39 p.m.