Triple
T32278113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hmong Thai script |
E824614
|
entity |
| Predicate | scriptEnvironment |
P65040
|
FINISHED |
| Object | Southeast Asia |
—
|
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: Southeast Asia | Statement: [Hmong Thai script, scriptEnvironment, Southeast Asia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptEnvironment Context triple: [Hmong Thai script, scriptEnvironment, Southeast Asia]
-
A.
programEnvironment
Indicates the contextual setting, conditions, and resources within which a program operates or is executed.
-
B.
scriptSystem
Indicates that one entity is the scripting or programming system used to control, configure, or automate the behavior of another entity.
-
C.
scriptDirectory
Indicates the directory path where a given script is located or stored.
-
D.
scriptSource
Indicates that one entity is the origin or provider of the script used or referenced by another entity.
-
E.
scriptCodeContext
chosen
Indicates that a script is written or executed within a particular code context or environment.
- 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_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 1, 2026, 12:43 a.m.