Triple
T26389511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krating Daeng |
E663373
|
entity |
| Predicate | writingSystemOfThaiName |
P454
|
FINISHED |
| Object | Thai script |
—
|
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: Thai script | Statement: [Krating Daeng, writingSystemOfThaiName, Thai script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingSystemOfThaiName Context triple: [Krating Daeng, writingSystemOfThaiName, Thai script]
-
A.
writingSystem
chosen
Indicates that one entity is the script or system of written symbols used to represent the language or content of another entity.
-
B.
writingSystemNameInKorean
Indicates that the predicate specifies the name of a writing system as expressed in the Korean language.
-
C.
writingSystemUsedIn
Indicates that a particular writing system is employed for written communication within a given language, region, or context.
-
D.
writingSystemDevelopedFor
Indicates that a particular writing system was created or adapted specifically to be used for a given language, community, or purpose.
-
E.
writingSystemStandardized
Indicates that a writing system has been formally codified and regulated according to an accepted standard or set of rules.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610be3e848190b7acb7675e37e1f5 |
completed | May 2, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 11:24 p.m.