Triple

T32278112
Position Surface form Disambiguated ID Type / Status
Subject Hmong Thai script E824614 entity
Predicate writingSystemStatusInThailand P7443 FINISHED
Object community-based 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: community-based | Statement: [Hmong Thai script, writingSystemStatusInThailand, community-based]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: writingSystemStatusInThailand
Context triple: [Hmong Thai script, writingSystemStatusInThailand, community-based]
  • A. writingSystemStatus chosen
    Indicates the current functional or sociolinguistic state of a writing system, such as whether it is actively used, obsolete, official, or endangered.
  • B. statusInThailand
    Indicates the legal, social, or official standing or condition an entity holds specifically within the context of Thailand.
  • C. workStatusInThailand
    Indicates the current legal or employment status of a person with respect to working in Thailand.
  • D. writingSystem
    Indicates that one entity is the script or system of written symbols used to represent the language or content of another entity.
  • E. writingSystemUsedIn
    Indicates that a particular writing system is employed for written communication within a given language, region, or context.
  • 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_69f3490f404081908450db66884f4334 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6bcc5e6608190afd4e2b9e6774f5e completed May 3, 2026, 3:11 a.m.
PD Predicate disambiguation batch_69f6b632cf788190a3d0c08cd026b84b completed May 3, 2026, 2:42 a.m.
Created at: May 1, 2026, 12:43 a.m.