Triple

T23916132
Position Surface form Disambiguated ID Type / Status
Subject Angan languages E602085 entity
Predicate areSpokenBy P2181 FINISHED
Object Angan peoples
The Angan peoples are indigenous ethnic groups of Papua New Guinea and nearby regions, known for their distinct cultural traditions and use of the Angan language family.
E1825885 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: Angan peoples | Statement: [Angan languages, areSpokenBy, Angan peoples]
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: Angan peoples
Triple: [Angan languages, areSpokenBy, Angan peoples]
Generated description
The Angan peoples are indigenous ethnic groups of Papua New Guinea and nearby regions, known for their distinct cultural traditions and use of the Angan language family.

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_69e2953a187081908346a9f36e85fc98 completed April 17, 2026, 8:16 p.m.
NER Named-entity recognition batch_69f1ce9a744c819080bd30176b8de9a0 completed April 29, 2026, 9:25 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2e657136d4819089b0a177b3167ef2 completed June 14, 2026, 8:25 a.m.
NEDg Description generation batch_6a2e75664e48819095987fd4bb25c136 completed June 14, 2026, 9:33 a.m.
NED2 Entity disambiguation (via description) batch_6a2e761b73e08190992378beb214bc47 completed June 14, 2026, 9:36 a.m.
Created at: April 17, 2026, 8:40 p.m.