Triple

T31155594
Position Surface form Disambiguated ID Type / Status
Subject Tindi language E794196 entity
Predicate spokenBy P2181 FINISHED
Object Tindi people
The Tindi people are a small indigenous ethnic group from Dagestan in the North Caucasus, known for their distinct Northeast Caucasian language and traditional mountain lifestyle.
E2292987 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: Tindi people | Statement: [Tindi language, spokenBy, Tindi people]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Tindi people
Triple: [Tindi language, spokenBy, Tindi people]
Generated description
The Tindi people are a small indigenous ethnic group from Dagestan in the North Caucasus, known for their distinct Northeast Caucasian language and traditional mountain lifestyle.

Provenance (5 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_69f224d41bb48190a5621cd1485e3a30 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f697f3d0e881909ec6c3e2cfbed20f completed May 3, 2026, 12:33 a.m.
NED1 Entity disambiguation (via context triple) batch_6a7a4b28973c819082fb1ccd5261515b completed Aug. 10, 2026, 10:05 p.m.
NEDg Description generation batch_6a7a4c36d50881908465b2dcb94f35b8 completed Aug. 10, 2026, 10:09 p.m.
NED2 Entity disambiguation (via description) batch_6a7a4c95746c8190859e6bd1fc8d4511 completed Aug. 10, 2026, 10:11 p.m.
Created at: April 29, 2026, 9:06 p.m.