Triple
T13299246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thai language |
E316763
|
entity |
| Predicate | hasWritingSystemSinceCentury |
P11432
|
FINISHED |
| Object | 13th century |
—
|
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: 13th century | Statement: [Thai language, hasWritingSystemSinceCentury, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWritingSystemSinceCentury Context triple: [Thai language, hasWritingSystemSinceCentury, 13th century]
-
A.
hasOfficialWritingSystem
Indicates that an entity (typically a language) is associated with a formally recognized and standardized writing system used for official or standard purposes.
-
B.
hasWritingTraditionSince
Indicates that a writing tradition has been present or established for an entity starting from a specified point in time.
-
C.
hasOrthographyDeveloped
Indicates that an entity’s writing system or spelling conventions have been created, established, or brought to a more advanced or standardized form.
-
D.
writingSystemHistorically
Indicates that one writing system was historically used for, associated with, or served as a predecessor to another writing system.
-
E.
writingSystemUsedSince
chosen
Indicates that a particular writing system has been in use starting from a specified point in time or period.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6893708190aeebf4c47386cff7 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:28 p.m.