Triple

T29770950
Position Surface form Disambiguated ID Type / Status
Subject Ma’anyan E755247 entity
Predicate spokenBy P2181 FINISHED
Object Ma’anyan people
The Ma’anyan people are an indigenous Dayak ethnic group of Central Kalimantan, Indonesia, known for their distinct Austronesian language and traditional riverine, forest-based culture.
E2004953 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: Ma’anyan people | Statement: [Ma’anyan, spokenBy, Ma’anyan 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: Ma’anyan people
Triple: [Ma’anyan, spokenBy, Ma’anyan people]
Generated description
The Ma’anyan people are an indigenous Dayak ethnic group of Central Kalimantan, Indonesia, known for their distinct Austronesian language and traditional riverine, forest-based culture.

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_69f0ef878574819088c867fd1a5c8b86 completed April 28, 2026, 5:33 p.m.
NER Named-entity recognition batch_69f674622e388190b61daf41825daf0f completed May 2, 2026, 10:02 p.m.
NED1 Entity disambiguation (via context triple) batch_6a344ee08d588190a92e4fa5e14250f1 completed June 18, 2026, 8:02 p.m.
NEDg Description generation batch_6a344f9edee08190b40cf3f1eb51f8a8 completed June 18, 2026, 8:05 p.m.
NED2 Entity disambiguation (via description) batch_6a34513c68008190829e0525a5a0c9bc completed June 18, 2026, 8:12 p.m.
Created at: April 28, 2026, 8:42 p.m.