Triple

T36305027
Position Surface form Disambiguated ID Type / Status
Subject Shui language E893921 entity
Predicate traditionalScriptUse P17239 FINISHED
Object ritual texts LITERAL 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: ritual texts | Statement: [Shui language, traditionalScriptUse, ritual texts]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: traditionalScriptUse
Context triple: [Shui language, traditionalScriptUse, ritual texts]
  • A. traditionalText
    Indicates that the associated text is expressed in a traditional or historically established form, style, or script as opposed to a modern or simplified variant.
  • B. traditionalLanguageType
    Indicates that an entity’s language belongs to a traditional or historically established linguistic type or category.
  • C. formerScript chosen
    Indicates that an entity previously served as the script or writing system for another entity, but is no longer used in that role.
  • D. traditionalStyle
    Indicates that something follows or embodies a conventional, long-established way of doing, making, or presenting it, in contrast to modern or innovative styles.
  • E. traditionalSee
    Indicates that one entity perceives or views another entity in a conventional or customary manner, following established norms or traditions.
  • F. None of above.

Provenance (3 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_69ff84df768c81908c65a1a7e33103ad completed May 9, 2026, 7:02 p.m.
PD Predicate disambiguation batch_69ff848d0af881908ee42c27a58af47e completed May 9, 2026, 7:01 p.m.
Created at: May 3, 2026, 4:09 p.m.