Triple

T19396186
Position Surface form Disambiguated ID Type / Status
Subject Tabasaran people E485192 entity
Predicate selfIdentification P4296 FINISHED
Object Tabasaran 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: Tabasaran | Statement: [Tabasaran people, selfIdentification, Tabasaran]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tabasaran
Context triple: [Tabasaran people, selfIdentification, Tabasaran]
  • A. Tabasaran chosen
    Tabasaran is a Northeast Caucasian language spoken primarily by the Tabasaran people in southern Dagestan, Russia.
  • B. Takabisha
    Takabisha is a record-breaking steel roller coaster in Japan renowned for its extremely steep drop and intense thrill elements.
  • C. Perenaar
    A Perenaar is a person who originates from or is a resident of the place called Peer.
  • D. Nabitasan
    Nabitasan is a barangay (village-level administrative division) of the municipality of Oton in the province of Iloilo, Philippines.
  • E. Talifuguen
    Talifuguen is a dialect of the Isnag language spoken by indigenous communities in the northern Philippines.
  • 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_69d8e8d5162481909db12435d9535c1a completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e62573f5788190a635b92121db2cf7 completed April 20, 2026, 1:09 p.m.
Created at: April 10, 2026, 1:36 p.m.