Triple
T24123071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 8859-3 |
E597716
|
entity |
| Predicate | graphicCharacterRange |
P23705
|
FINISHED |
| Object | 160–255 |
—
|
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: 160–255 | Statement: [ISO/IEC 8859-3, graphicCharacterRange, 160–255]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: graphicCharacterRange Context triple: [ISO/IEC 8859-3, graphicCharacterRange, 160–255]
-
A.
printableCharacterRange
chosen
Indicates the range of characters that are considered printable within a given character set or encoding.
-
B.
unicodeRangeStart
Indicates the starting code point in Unicode for a specified range of characters or symbols.
-
C.
characterCoverage
Indicates that one entity provides or includes sufficient representation or support for the characters (e.g., glyphs, symbols, or scripts) required or used by another entity.
-
D.
unicodeRangeHex
Indicates that a character or set of characters falls within a specified range of Unicode code points expressed in hexadecimal notation.
-
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_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.