Triple
T38309172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TR4 |
E1033637
|
entity |
| Predicate | supportsUnlockedCPUs |
P204595
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [TR4, supportsUnlockedCPUs, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsUnlockedCPUs Context triple: [TR4, supportsUnlockedCPUs, yes]
-
A.
supportsProcessorCoreCount
Indicates that one entity is compatible with or able to operate using a specified number of processor cores in another entity.
-
B.
supportedCPU
Indicates that a given CPU model or architecture is compatible with and can be used by a particular system, device, or software.
-
C.
supportsIntelHyperThreading
Indicates that one entity provides compatibility with or functionality for Intel Hyper-Threading technology in relation to another entity.
-
D.
supportsHyperThreading
Indicates that one entity provides or enables Hyper-Threading capability for another entity.
-
E.
supportsSymmetricMultiprocessing
Indicates that an entity provides or is compatible with symmetric multiprocessing, allowing multiple processors to share memory and workload equally.
- F. None of above. chosen
Provenance (4 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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:30 p.m.