Triple
T29672163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun 4/110 |
E750703
|
entity |
| Predicate | hasMainProcessorType |
P186412
|
FINISHED |
| Object | SPARC RISC processor |
—
|
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: SPARC RISC processor | Statement: [Sun 4/110, hasMainProcessorType, SPARC RISC processor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainProcessorType Context triple: [Sun 4/110, hasMainProcessorType, SPARC RISC processor]
-
A.
mainProcessorType
chosen
Indicates the type or category of processor that serves as the primary or central processing unit for a given system or device.
-
B.
hasBuiltInProcessor
Indicates that one entity inherently contains an integrated processor as a built-in component rather than relying on an external processing unit.
-
C.
hasMainArch
Indicates that an entity possesses or features a primary or central arch structure.
-
D.
hasMainOperations
Indicates that an entity is associated with its primary or core operations, activities, or functions.
-
E.
hasMainKeepType
Indicates the specific type or category of main keep associated with a structure or site.
- 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff6074bcd4819090b72cd6209ff206 |
completed | May 9, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69ff600aba888190812a6e7eca0283b8 |
completed | May 9, 2026, 4:25 p.m. |
Created at: April 28, 2026, 7:05 p.m.