Triple

T36610348
Position Surface form Disambiguated ID Type / Status
Subject Nampeyo E903448 entity
Predicate ethnicity P194 FINISHED
Object Hopi-Tewa
Hopi-Tewa refers to a Puebloan community of Tewa-speaking people who migrated to and settled among the Hopi in northeastern Arizona, maintaining distinct cultural and artistic traditions.
E2198061 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: Hopi-Tewa | Statement: [Nampeyo, ethnicity, Hopi-Tewa]
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: Hopi-Tewa
Triple: [Nampeyo, ethnicity, Hopi-Tewa]
Generated description
Hopi-Tewa refers to a Puebloan community of Tewa-speaking people who migrated to and settled among the Hopi in northeastern Arizona, maintaining distinct cultural and artistic traditions.

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_69f76e6960e4819092047756ceb9a17e completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7c47bc42c81909070f521cdc4e0d0 completed May 3, 2026, 9:56 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3c1718307c8190acfca477b691ff6f completed June 24, 2026, 5:42 p.m.
NEDg Description generation batch_6a3c17bef5988190bf7bbafbaaeebef1 completed June 24, 2026, 5:45 p.m.
NED2 Entity disambiguation (via description) batch_6a3c6c139c748190befd6b09cf6171b2 completed June 24, 2026, 11:45 p.m.
Created at: May 3, 2026, 4:11 p.m.