Triple

T29820885
Position Surface form Disambiguated ID Type / Status
Subject Dayak Luangan E757239 entity
Predicate hasSubgroup P747 FINISHED
Object Tunjung people
The Tunjung people are an indigenous Dayak subgroup of Borneo known for their distinct language, traditional longhouse communities, and rich ritual and artistic heritage.
E1811963 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: Tunjung people | Statement: [Dayak Luangan, hasSubgroup, Tunjung 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: Tunjung people
Triple: [Dayak Luangan, hasSubgroup, Tunjung people]
Generated description
The Tunjung people are an indigenous Dayak subgroup of Borneo known for their distinct language, traditional longhouse communities, and rich ritual and artistic heritage.

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_69f2245701c88190ad42415a0956c4ed completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69f675675250819089db3b30f1f05f87 completed May 2, 2026, 10:06 p.m.
NED1 Entity disambiguation (via context triple) batch_6a37cfc5b2e48190bf66a65671ee9744 completed June 21, 2026, 11:49 a.m.
NEDg Description generation batch_6a37d07ba708819081b552b8a69313e5 completed June 21, 2026, 11:52 a.m.
NED2 Entity disambiguation (via description) batch_6a37d1935d9881909cee3755fec2d996 completed June 21, 2026, 11:57 a.m.
Created at: April 29, 2026, 5:29 p.m.