Triple
T6442087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 8859 |
E138248
|
entity |
| Predicate | characterSize |
P57048
|
FINISHED |
| Object | single-byte |
—
|
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: single-byte | Statement: [ISO/IEC 8859, characterSize, single-byte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterSize Context triple: [ISO/IEC 8859, characterSize, single-byte]
-
A.
characterStyle
chosen
Indicates how a character is visually or typographically presented, such as its font, weight, size, or decorative attributes.
-
B.
characterSetSize
Indicates the total number of distinct characters contained in or allowed by a given character set.
-
C.
character2
Indicates that a second character entity is involved in the relationship or context defined by the predicate.
-
D.
characterCellResolution
Indicates a relationship where the visual or logical representation of characters is determined or adjusted at the level of individual cells (e.g., grid units or display slots).
-
E.
textCharacter
Indicates that one entity is a character (such as a letter, digit, or symbol) within a piece of text associated with another entity.
- 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06989dfb88190b25ff8b2c53f3ced |
completed | March 22, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69c060faaf248190bbdc8ff909c8777a |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:46 p.m.