Triple
T13275918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HEBREW LETTER FINAL PE |
E316188
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Unicode character |
C32759
|
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 Context triple: [HEBREW LETTER FINAL PE, instanceOf, Unicode character]
-
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 character property
A Unicode character property is an attribute defined by the Unicode Standard that describes a specific aspect of a character’s behavior, appearance, or classification, such as its script, category, or bidirectional behavior.
-
C.
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.
-
D.
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.
-
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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:26 p.m.