Triple
T1079893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASCII |
E23922
|
entity |
| Predicate | definesCodePoints |
P5708
|
FINISHED |
| Object | 128 |
—
|
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: 128 | Statement: [ASCII, definesCodePoints, 128]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesCodePoints Context triple: [ASCII, definesCodePoints, 128]
-
A.
UnicodeCodePointLowercase
Indicates that one Unicode code point is the lowercase mapping or lowercase equivalent of another code point.
-
B.
codeSpaceRange
chosen
Indicates the range of code points or values that define the valid span or interval within a given code space.
-
C.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
-
D.
numericCode
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
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.