Triple

T24559490
Position Surface form Disambiguated ID Type / Status
Subject Zapin Melayu E607611 entity
Predicate hasRegionalVariant P5595 FINISHED
Object Zapin Betawi
Zapin Betawi is a Jakarta-based variant of the traditional Malay zapin dance, blending Islamic-influenced movements with local Betawi music and cultural elements.
E1640411 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: Zapin Betawi | Statement: [Zapin Melayu, hasRegionalVariant, Zapin Betawi]
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: Zapin Betawi
Triple: [Zapin Melayu, hasRegionalVariant, Zapin Betawi]
Generated description
Zapin Betawi is a Jakarta-based variant of the traditional Malay zapin dance, blending Islamic-influenced movements with local Betawi music and cultural elements.

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_69e2c4cae1b88190825e88d5ce8aa61e completed April 17, 2026, 11:39 p.m.
NER Named-entity recognition batch_69f2a8f4af6481908576473adab9f6bf completed April 30, 2026, 12:57 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0ff8650d688190b662bac51f5cbd07 completed May 22, 2026, 6:32 a.m.
NEDg Description generation batch_6a0ff97de1608190b0f6e6117241e563 completed May 22, 2026, 6:36 a.m.
NED2 Entity disambiguation (via description) batch_6a0ffa00b57081909bc69474734fcb20 completed May 22, 2026, 6:38 a.m.
Created at: April 18, 2026, 2:27 a.m.