Triple
T6441986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supplementary Special-purpose Plane |
E138246
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ISO/IEC 10646 code plane |
C20144
|
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: ISO/IEC 10646 code plane Context triple: [Supplementary Special-purpose Plane, instanceOf, ISO/IEC 10646 code plane]
-
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 standard
The Unicode standard is a universal character encoding system that assigns a unique code point to virtually every written symbol, enabling consistent text representation and processing across different platforms, languages, and devices.
-
C.
Unicode project
A Unicode project is an initiative focused on implementing, extending, or utilizing the Unicode standard to support consistent encoding, representation, and processing of text across different languages and platforms.
-
D.
version of the Unicode Standard
A version of the Unicode Standard is a specific, numbered release of the Unicode specification that defines the set of encoded characters, properties, and related algorithms valid at that point in the standard’s evolution.
-
E.
Unicode technical standard
A Unicode technical standard is a formal specification published by the Unicode Consortium that defines detailed rules, algorithms, or data formats extending or clarifying the core Unicode Standard for consistent text processing across systems.
- F. None of above. chosen
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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:46 p.m.