Triple

T37635920

Position	Surface form	Disambiguated ID	Type / Status
Subject	Udarata Natum	`E936486`	entity
Predicate	hasSubstyle	`P3485`	FINISHED
Object	Pantheru dance Pantheru dance is a traditional Kandyan sub-style characterized by the use of small hand-held tambourine-like instruments and energetic, rhythmic movements.	`E2235532`	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: Pantheru dance | Statement: [Udarata Natum, hasSubstyle, Pantheru dance]

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: Pantheru dance
Triple: [Udarata Natum, hasSubstyle, Pantheru dance]

Generated description

Pantheru dance is a traditional Kandyan sub-style characterized by the use of small hand-held tambourine-like instruments and energetic, rhythmic movements.

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_69f76ed31d8881908405da6c6d2f0463`	completed	May 3, 2026, 3:50 p.m.
NER	Named-entity recognition	`batch_69fba961676c8190b55a4638a206ed54`	completed	May 6, 2026, 8:49 p.m.
NED1	Entity disambiguation (via context triple)	`batch_6a40aff985b88190ad14f7c8726937f1`	completed	June 28, 2026, 5:24 a.m.
NEDg	Description generation	`batch_6a40b11c65048190a5b3e0eba7b902c0`	completed	June 28, 2026, 5:29 a.m.
NED2	Entity disambiguation (via description)	`batch_6a40b1a8db08819096ff4f042c166f0b`	completed	June 28, 2026, 5:31 a.m.

Created at: May 3, 2026, 4:18 p.m.