Triple
T32278107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hmong Thai script |
E824614
|
entity |
| Predicate | usageComparedTo |
P156221
|
FINISHED |
| Object | Romanized Popular Alphabet |
—
|
NE NERFINISHED |
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: Romanized Popular Alphabet | Statement: [Hmong Thai script, usageComparedTo, Romanized Popular Alphabet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usageComparedTo Context triple: [Hmong Thai script, usageComparedTo, Romanized Popular Alphabet]
-
A.
comparisonUses
Indicates that one entity employs another entity as a basis or tool for making a comparison.
-
B.
usageAmong
Indicates how frequently or in what manner something is used within a particular group, context, or population.
-
C.
usageType
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
-
D.
usageCategory
Indicates the classification of how something is used or the type of usage it falls under.
-
E.
comparisonUnit
chosen
Indicates that one entity serves as the reference or baseline unit against which another entity is compared or measured.
- 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.