Triple
T32278109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hmong Thai script |
E824614
|
entity |
| Predicate | associatedLanguageVarieties |
P152424
|
FINISHED |
| Object | Hmong Daw |
E237630
|
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: Hmong Daw | Statement: [Hmong Thai script, associatedLanguageVarieties, Hmong Daw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedLanguageVarieties Context triple: [Hmong Thai script, associatedLanguageVarieties, Hmong Daw]
-
A.
languageVarietyRegionOf
Indicates that a particular language variety is associated with or used in a specific geographic region.
-
B.
denotesLanguageVariety
chosen
Indicates that one entity specifies the particular variety, dialect, or form of language used or associated with another entity.
-
C.
hasLinguisticVariety
Indicates that one entity possesses or exhibits a particular linguistic variety in relation to another entity or context.
-
D.
linguisticVariant
Indicates that one linguistic form is an alternative version or expression of another within the same or closely related language context.
-
E.
languageVariants
Indicates that one language form is a variant or alternative version of another language.
- F. None of above.
Provenance (4 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_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f46e583dc8190be311b497dd0df04 |
completed | June 15, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:43 a.m.