Triple
T1079878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UTF-32 |
E23921
|
entity |
| Predicate | codeUnitSize |
P8899
|
FINISHED |
| Object | 4 bytes |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 4 bytes | Statement: [UTF-32, codeUnitSize, 4 bytes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeUnitSize Context triple: [UTF-32, codeUnitSize, 4 bytes]
-
A.
codingSystemType
Indicates the classification or category of coding system used to encode or represent information in a given context.
-
B.
nativeUnit
chosen
Indicates that one unit is the original, inherent, or default measurement unit associated with a given quantity or entity.
-
C.
typicalUnitSize
Indicates the standard or most common size or quantity in which something is typically measured, packaged, or used.
-
D.
hasGlyphRepertoireSize
Indicates the number of distinct glyphs included in an entity’s glyph repertoire.
-
E.
UnicodeBlock
Indicates that a character belongs to a specific contiguous range of code points defined as a Unicode block.
- F. None of above.
Provenance (3 batches)
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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b94509d08190964509ea4a2d7912 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73d9f08819093668104f129840e |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.