Triple

T25118540
Position Surface form Disambiguated ID Type / Status
Subject Arifin Ilham E629201 entity
Predicate ethnicGroup P194 FINISHED
Object Buginese
The Buginese are an Austronesian ethnic group from South Sulawesi, Indonesia, known for their seafaring traditions, maritime trade, and distinctive Bugis language and culture.
E128374 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: Buginese | Statement: [Arifin Ilham, ethnicGroup, Buginese]
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: Buginese
Triple: [Arifin Ilham, ethnicGroup, Buginese]
Generated description
The Buginese are an Austronesian ethnic group from South Sulawesi, Indonesia, known for their seafaring traditions, maritime trade, and distinctive Bugis language and 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_69e2ff3169d08190973b6061d5009abd completed April 18, 2026, 3:49 a.m.
NER Named-entity recognition batch_69f465c9bad88190b1488ada06e9b51b completed May 1, 2026, 8:35 a.m.
NED1 Entity disambiguation (via context triple) batch_6a1048faeae88190a09c7e5ed04aa2f9 completed May 22, 2026, 12:15 p.m.
NEDg Description generation batch_6a10498fb6548190b050f4d94f373f43 completed May 22, 2026, 12:18 p.m.
NED2 Entity disambiguation (via description) batch_6a104a151da88190a2d8aba44f1dd924 completed May 22, 2026, 12:20 p.m.
Created at: April 18, 2026, 6:27 a.m.