Triple
T28898653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shift JIS |
E732895
|
entity |
| Predicate | codePageOwner |
P152053
|
FINISHED |
| Object | Microsoft Windows |
—
|
NE NERFINISHED |
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: Microsoft Windows | Statement: [Shift JIS, codePageOwner, Microsoft Windows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codePageOwner Context triple: [Shift JIS, codePageOwner, Microsoft Windows]
-
A.
codePageNumber
Indicates the specific page number within a code document or code listing where something is located or referenced.
-
B.
codenameOwner
Indicates that one entity is the designated owner or holder of the specified codename associated with another entity.
-
C.
usesCodePageLayout
Indicates that one entity arranges or interprets character data according to the code page layout defined or provided by another entity.
-
D.
hasCodePageRelationship
chosen
Indicates a relationship where one entity is associated with, linked to, or defined in terms of a specific code page or character encoding scheme.
-
E.
programOwner
Indicates that one entity is the primary responsible owner or controller of a particular program 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_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.