Triple
T4381722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elxsi |
E99144
|
entity |
| Predicate | systemArchitecture |
P4621
|
FINISHED |
| Object | multiprocessor |
—
|
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: multiprocessor | Statement: [Elxsi, systemArchitecture, multiprocessor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemArchitecture Context triple: [Elxsi, systemArchitecture, multiprocessor]
-
A.
graphicsArchitecture
Indicates the underlying design or structural framework that defines how a system’s graphics or visual rendering components are organized and operate.
-
B.
cpuArchitecture
Indicates the type of processor instruction set or hardware architecture that a computing system or component is designed to run on.
-
C.
architecture
chosen
Indicates the structural design or organizational framework that defines how components of a system or entity are arranged and interact.
-
D.
system
Indicates that an entity functions as or belongs to a structured, organized set of components or processes that operate together as a system.
-
E.
computerSystem
Indicates a relationship where an entity functions as or is classified as a computer system, typically comprising hardware, software, and related components that operate together.
- 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_69b3454ea8f48190a49c2436624d6ef6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352613dd481909e008a8db239a108 |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f557fe8819085032bf7f0cea5dc |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:18 p.m.