Triple
T29858328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATI Xenos |
E758248
|
entity |
| Predicate | coreClock |
P8610
|
FINISHED |
| Object | approximately 500 MHz |
—
|
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: approximately 500 MHz | Statement: [ATI Xenos, coreClock, approximately 500 MHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreClock Context triple: [ATI Xenos, coreClock, approximately 500 MHz]
-
A.
clockSpeed
chosen
Indicates the operating frequency at which a clock-driven component (such as a processor) performs its cycles or operations over time.
-
B.
hasClockSpeed
Indicates that an entity (typically a processor or device) operates at a specified clock frequency or speed.
-
C.
minClockSpeed
Indicates the minimum operating clock speed required or supported for a given hardware component or system.
-
D.
coreVoltage
Indicates the electrical potential difference supplied to the core component of a device or system.
-
E.
hasInternalFrequencyCompensation
Indicates that an electronic component or circuit includes built-in circuitry to stabilize its frequency response without requiring external compensation components.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6768345fc8190bdc72aa7af054375 |
completed | May 2, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:47 p.m.