Triple
T8286695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SuperH |
E193802
|
entity |
| Predicate | hasVersion |
P455
|
FINISHED |
| Object | SH-4 |
E724159
|
NE 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: SH-4 | Statement: [SuperH, hasVersion, SH-4]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SH-4 Context triple: [SuperH, hasVersion, SH-4]
-
A.
SH-1
SH-1 is the first-generation implementation of the SuperH 32-bit RISC microprocessor architecture developed for embedded systems.
-
B.
SH4
chosen
SH4 is a 32-bit RISC microprocessor architecture from Hitachi’s SuperH family, widely used in embedded systems and notably in the Sega Dreamcast console.
-
C.
SH-2
SH-2 is a 32-bit member of the SuperH family of RISC microprocessor cores, used in embedded systems for efficient, low-power computing.
-
D.
SH 45
SH 45 is a state highway in Colorado that serves as a key north–south route in the city of Pueblo.
-
E.
SR 400
SR 400 is a major north–south highway in Georgia that serves as a key commuter and traffic corridor through the Atlanta metropolitan area.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7ad3722481908076508908d18621 |
completed | March 31, 2026, 7:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd952399dc8190914951d4e9e36c38 |
completed | April 1, 2026, 9:58 p.m. |
Created at: March 30, 2026, 5:52 p.m.