Triple
T30405133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM Roadrunner |
E773457
|
entity |
| Predicate | usedProcessorModel |
P12004
|
FINISHED |
| Object | AMD Opteron |
—
|
NE NERFINISHED |
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: AMD Opteron | Statement: [IBM Roadrunner, usedProcessorModel, AMD Opteron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedProcessorModel Context triple: [IBM Roadrunner, usedProcessorModel, AMD Opteron]
-
A.
usedProcess
Indicates that an entity employed or applied a particular process to achieve a result or perform an action.
-
B.
usesProcessorSeries
chosen
Indicates that one entity operates using, or is built to run on, a specific series or family of processors.
-
C.
usesProcessorBrand
Indicates that one entity employs or is built with a processor manufactured by the specified brand.
-
D.
usedProgramModel
Indicates that an entity employed a specific program model as the basis or framework for its activities or operations.
-
E.
usesProductionModel
Indicates that one entity employs or relies on another entity as its primary or official production model in practice.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:03 p.m.