Triple

T23623026
Position Surface form Disambiguated ID Type / Status
Subject Baram Kayan E583373 entity
Predicate relatedTo P37 FINISHED
Object Kayan Busang
Kayan Busang is an indigenous Kayan subgroup from the interior regions of Borneo, known for their distinct language, traditional longhouse communities, and rich cultural practices.
E1602603 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: Kayan Busang | Statement: [Baram Kayan, relatedTo, Kayan Busang]
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: Kayan Busang
Triple: [Baram Kayan, relatedTo, Kayan Busang]
Generated description
Kayan Busang is an indigenous Kayan subgroup from the interior regions of Borneo, known for their distinct language, traditional longhouse communities, and rich cultural practices.

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_69e248fc8d74819091bd5baef2f36f6f completed April 17, 2026, 2:51 p.m.
NER Named-entity recognition batch_69f1b17ae58c8190b7b6cdc57c6ead3a completed April 29, 2026, 7:21 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0f53998e908190a4a5823290cbd8b2 completed May 21, 2026, 6:48 p.m.
NEDg Description generation batch_6a0f57dcde28819083a78f276a1038a3 completed May 21, 2026, 7:07 p.m.
NED2 Entity disambiguation (via description) batch_6a0f58be2c44819085064c63d07e6906 completed May 21, 2026, 7:10 p.m.
Created at: April 17, 2026, 6:46 p.m.