Triple

T27874039
Position Surface form Disambiguated ID Type / Status
Subject Ntumbu tuta E704876 entity
Predicate associatedWith P37 FINISHED
Object Bima culture
Bima culture is the traditional cultural heritage of the Bima people of eastern Sumbawa in Indonesia, characterized by distinct customs, language, arts, and social practices.
E1794050 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: Bima culture | Statement: [Ntumbu tuta, associatedWith, Bima culture]
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: Bima culture
Triple: [Ntumbu tuta, associatedWith, Bima culture]
Generated description
Bima culture is the traditional cultural heritage of the Bima people of eastern Sumbawa in Indonesia, characterized by distinct customs, language, arts, and social 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_69ef84111bb4819084298f994b31c62f completed April 27, 2026, 3:43 p.m.
NER Named-entity recognition batch_69f6397e95908190bae6cfcd65e3fc20 completed May 2, 2026, 5:50 p.m.
NED1 Entity disambiguation (via context triple) batch_6a13034eb2188190a44ccd3ffdaf55a2 completed May 24, 2026, 1:55 p.m.
NEDg Description generation batch_6a1303fd53888190856a4b6e2b5f5dd5 completed May 24, 2026, 1:58 p.m.
NED2 Entity disambiguation (via description) batch_6a1304b2a0c481909283b9cafea6b075 completed May 24, 2026, 2:01 p.m.
Created at: April 27, 2026, 6:26 p.m.