Triple
T6398408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sentence_Break |
E143997
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Unicode character property |
C20399
|
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 character property Context triple: [Sentence_Break, instanceOf, Unicode character property]
-
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.
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.
-
E.
Unicode technical report
A Unicode technical report is an official document published by the Unicode Consortium that provides detailed guidance, clarifications, or extensions to the Unicode Standard on specific topics such as text processing, encoding, or implementation practices.
- 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_69c008dc56fc81908d43ffcc11d73bdd |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 4:35 p.m.