Triple
T28898628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shift JIS |
E732895
|
entity |
| Predicate | encodingFor |
P1444
|
FINISHED |
| Object | Japanese language |
—
|
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: Japanese language | Statement: [Shift JIS, encodingFor, Japanese language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encodingFor Context triple: [Shift JIS, encodingFor, Japanese language]
-
A.
encodingBasisFor
Indicates that one encoding scheme serves as the foundational or reference basis for defining or interpreting another encoding.
-
B.
localEncoding
Indicates that an entity is represented or stored using a specific encoding scheme that is defined or applied locally within a particular context or system.
-
C.
encodedIn
chosen
Indicates that one entity is represented, stored, or expressed within another entity using a specific encoding or format.
-
D.
encodes
Indicates that one entity contains or represents the information, instructions, or structure of another in a coded or symbolic form.
-
E.
encodingLibrary
Indicates that one entity is the software library or tool used to encode, transform, or serialize the other entity’s data or content.
- 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.