Triple
T28612845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SH-1 |
E724208
|
entity |
| Predicate | belongsToArchitectureLine |
P40829
|
FINISHED |
| Object | SuperH 32-bit RISC family |
—
|
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: SuperH 32-bit RISC family | Statement: [SH-1, belongsToArchitectureLine, SuperH 32-bit RISC family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToArchitectureLine Context triple: [SH-1, belongsToArchitectureLine, SuperH 32-bit RISC family]
-
A.
belongsToArchitectureModel
Indicates that something is a component or element that is contained within, defined by, or associated with a particular architecture model.
-
B.
hasArchitectureBy
Indicates that an entity’s architectural design was created or authored by a specified architect or architectural firm.
-
C.
belongsToProductLine
chosen
Indicates that an item or product is associated with and classified under a specific product line.
-
D.
usesArchitectureComponent
Indicates that one entity employs or incorporates a specific architecture component as part of its structure, design, or implementation.
-
E.
belongsToLine
Indicates that an entity is a member or component of a particular line or linear grouping.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: April 28, 2026, 4:30 a.m.