Triple
T32180072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hmng |
E821954
|
entity |
| Predicate | appliesToWritingSystem |
P197988
|
FINISHED |
| Object | Pahawh Hmong writing system |
—
|
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: Pahawh Hmong writing system | Statement: [Hmng, appliesToWritingSystem, Pahawh Hmong writing system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToWritingSystem Context triple: [Hmng, appliesToWritingSystem, Pahawh Hmong writing system]
-
A.
hasWritingSystemName
Indicates that a writing system is associated with a particular name or designation.
-
B.
hasCommonWritingSystem
Indicates that two entities use the same or mutually intelligible writing system for written communication.
-
C.
hasWritingSystemForMajorLanguage
Indicates that there exists a writing system used to represent a major language associated with the given entity.
-
D.
writingSystemFeatures
Indicates the specific structural or functional characteristics that define how a particular writing system represents language.
-
E.
hasWritingSystemProperty
Indicates that a writing system possesses a specific characteristic, feature, or attribute.
- F. None of above. chosen
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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
| PDg | Predicate description generation | batch_69fec00e5c1c819083d174bb4bc35f29 |
completed | May 9, 2026, 5:03 a.m. |
Created at: May 1, 2026, 12:34 a.m.