Triple
T22050386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tertiary Ideographic Plane |
E544866
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Unicode code space region |
C20143
|
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: Unicode code space region Context triple: [Tertiary Ideographic Plane, instanceOf, Unicode code space region]
-
A.
Unicode block
A Unicode block is a contiguous range of Unicode code points grouped together to organize characters with related scripts, symbols, or purposes.
-
B.
Unicode code plane
chosen
A Unicode code plane is a contiguous range of 65,536 Unicode code points (from U+0000 to U+10FFFF divided into 17 such planes) used to organize characters into logical groups.
-
C.
ISO/IEC 10646 code plane
An ISO/IEC 10646 code plane is a contiguous range of 65,536 Unicode scalar values grouped together within the Universal Coded Character Set to organize and allocate characters by script, symbol set, or function.
-
D.
Unicode block collection
A Unicode block collection is an organized grouping of contiguous ranges of Unicode code points, each block typically representing characters from a particular script, symbol set, or functional category.
-
E.
Unicode property
A Unicode property is an attribute assigned to each Unicode code point (such as its category, script, or case behavior) that describes its characteristics and governs how it is processed and interpreted in text operations.
- 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:26 p.m.