Triple

T23839914
Position Surface form Disambiguated ID Type / Status
Subject Sora language E590957 entity
Predicate spokenBy P2181 FINISHED
Object Saora tribe
The Saora tribe is an indigenous Adivasi community of eastern India, primarily in Odisha and Andhra Pradesh, known for its distinct language, rich animist traditions, and vibrant ritual art.
E1608199 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: Saora tribe | Statement: [Sora language, spokenBy, Saora tribe]
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: Saora tribe
Triple: [Sora language, spokenBy, Saora tribe]
Generated description
The Saora tribe is an indigenous Adivasi community of eastern India, primarily in Odisha and Andhra Pradesh, known for its distinct language, rich animist traditions, and vibrant ritual art.

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_69e25d1de32c8190a907afe9c3d6cd6d completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1c886aab081909ad896abe383afb9 completed April 29, 2026, 8:59 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0f7616779881909a2242b5f82828fe completed May 21, 2026, 9:16 p.m.
NEDg Description generation batch_6a0f779a5d4c81909384a3c6a1312359 completed May 21, 2026, 9:22 p.m.
NED2 Entity disambiguation (via description) batch_6a0f7895a12c8190999f81b9b4cd7b9b completed May 21, 2026, 9:26 p.m.
Created at: April 17, 2026, 8:08 p.m.