Triple
T38315833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tham script |
E1033822
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic writing system |
C3166
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historic writing system Context triple: [Tham script, instanceOf, historic writing system]
-
A.
ancient writing system
An ancient writing system is a structured method of visually representing language used by early civilizations to record information, communicate, and preserve cultural, religious, or administrative knowledge.
-
B.
historic script
chosen
A historic script is a system of writing used by past civilizations or cultures that records their language, ideas, and events, often preserved in artifacts, manuscripts, or inscriptions.
-
C.
historical development of writing system
The historical development of writing systems traces the evolution of human communication from early pictographic marks to complex, standardized scripts used for recording language, culture, and knowledge across time and civilizations.
-
D.
historic communication system
A historic communication system is a method or infrastructure used in past eras to transmit information between people or places, such as telegraphs, postal services, or smoke signals.
-
E.
indigenous writing system
An indigenous writing system is a set of symbols and rules for written communication that originates from, is developed by, and reflects the linguistic and cultural practices of a specific native or aboriginal community.
- F. None of above.
Provenance (1 batch)
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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:30 p.m.