Triple
T24148870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 8859-13 |
E598468
|
entity |
| Predicate | hasByteValues128to255 |
P154787
|
FINISHED |
| Object | assigned to additional letters and symbols |
—
|
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: assigned to additional letters and symbols | Statement: [ISO/IEC 8859-13, hasByteValues128to255, assigned to additional letters and symbols]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasByteValues128to255 Context triple: [ISO/IEC 8859-13, hasByteValues128to255, assigned to additional letters and symbols]
-
A.
maxBytesPerCodePoint
Indicates the maximum number of bytes used to encode a single code point in a given character encoding or data representation.
-
B.
minBytesPerCodePoint
Indicates the minimum number of bytes required to represent a single code point in the given encoding or data representation.
-
C.
hasLetterValue
Indicates that a particular letter or character is associated with a specific numeric or symbolic value.
-
D.
hasControlCharacterRange
Indicates that there exists a specified range of control characters associated with or applicable to an entity.
-
E.
supportsByteAddressing
Indicates that one entity provides the capability for direct access to individual bytes within its addressable memory or data space for another entity.
- F. None of above. chosen
Provenance (4 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_69e288c9e488819093dd1acd91b08b8a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e00d252c8190a02bec29189baad0 |
completed | April 29, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69f176585f3481909beb907de252cd98 |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 11:30 p.m.