Triple

T36304786
Position Surface form Disambiguated ID Type / Status
Subject Sui people E893915 entity
Predicate writingSystem P454 FINISHED
Object Sui script
The Sui script is an indigenous logographic writing system used by the Sui people of China, notable for its ritual and divinatory functions and its limited number of specialized users.
E2179331 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: Sui script | Statement: [Sui people, writingSystem, Sui script]
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: Sui script
Triple: [Sui people, writingSystem, Sui script]
Generated description
The Sui script is an indigenous logographic writing system used by the Sui people of China, notable for its ritual and divinatory functions and its limited number of specialized users.

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_69f76e4c1b248190b10667d0213537fe completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7ba1ea2408190b08cafe75125f2a2 completed May 3, 2026, 9:11 p.m.
NED1 Entity disambiguation (via context triple) batch_6a397d842f1481908782c39664b5b68c completed June 22, 2026, 6:23 p.m.
NEDg Description generation batch_6a3991a5e578819094db7fca1ea7437b completed June 22, 2026, 7:48 p.m.
NED2 Entity disambiguation (via description) batch_6a39927c2c488190b0d23beee3e77909 completed June 22, 2026, 7:52 p.m.
Created at: May 3, 2026, 4:09 p.m.