Triple
T24638024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMD-103 P40DC |
E609866
|
entity |
| Predicate | hasOperatorClassDesignation |
P83225
|
FINISHED |
| Object | AMD-103 |
—
|
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: AMD-103 | Statement: [AMD-103 P40DC, hasOperatorClassDesignation, AMD-103]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOperatorClassDesignation Context triple: [AMD-103 P40DC, hasOperatorClassDesignation, AMD-103]
-
A.
operatorClassName
Indicates the classification or type name assigned to an operator within a system or model.
-
B.
operatorClass
chosen
Indicates the classification or category of an operator in terms of its type, role, or functional group within a system or domain.
-
C.
designedOperator
Indicates that an entity (typically a person or organization) intentionally created or planned the specified operator (such as a function, mechanism, or process) for a particular purpose.
-
D.
isOperatorOn
Indicates that one entity serves as an operator responsible for operating, controlling, or managing another entity (such as a system, machine, or process).
-
E.
hasMajorOperator
Indicates that an entity is primarily operated, managed, or run by a specified main operator or organization.
- 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_69e2c4d28f848190ac38c400060e943d |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be064ff88190b5d9e5ec75a41242 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d0ab708190b2e3b94dd20ca76b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:33 a.m.