Triple
T24123087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 8859-3 |
E597716
|
entity |
| Predicate | asciiRange |
P23705
|
FINISHED |
| Object | 0–127 identical to ASCII |
—
|
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: 0–127 identical to ASCII | Statement: [ISO/IEC 8859-3, asciiRange, 0–127 identical to ASCII]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: asciiRange Context triple: [ISO/IEC 8859-3, asciiRange, 0–127 identical to ASCII]
-
A.
alphabetRange
Indicates that one entity specifies a contiguous range of letters in an alphabet that extends from the starting letter to the ending letter.
-
B.
unicodeRangeStart
Indicates the starting code point in Unicode for a specified range of characters or symbols.
-
C.
unicodeRangeHex
Indicates that a character or set of characters falls within a specified range of Unicode code points expressed in hexadecimal notation.
-
D.
printableCharacterRange
chosen
Indicates the range of characters that are considered printable within a given character set or encoding.
-
E.
ISO8859-1Range0x80-0x9F
Indicates that a character falls within the 0x80–0x9F byte range of the ISO 8859-1 (Latin-1) character encoding.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dee5937c819092396751c23553ca |
completed | April 29, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:06 p.m.