Triple
T28898641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shift JIS |
E732895
|
entity |
| Predicate | byteStructure |
P28140
|
FINISHED |
| Object | single-byte characters |
—
|
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 characters | Statement: [Shift JIS, byteStructure, single-byte characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: byteStructure Context triple: [Shift JIS, byteStructure, single-byte characters]
-
A.
serialStructure
Indicates a relationship where components are arranged or connected in a sequential, one-after-another order, such that each element follows the previous in a linear chain.
-
B.
encodingStructure
chosen
Indicates the structural scheme or format used to encode information or data.
-
C.
recordStructure
Indicates a relationship where an entity defines, organizes, or specifies the internal layout and components of a record or data structure.
-
D.
storageStructure
Indicates a relationship where one entity serves as a physical or logical structure used to store or contain another entity.
-
E.
segmentStructure
Indicates that one entity represents a structural or organizational subdivision (a segment) within the overall structure of 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65aa5b40881908123b73bb40b1526 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 8:01 a.m.