Triple
T31317161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USBMR1400128 |
E798626
|
entity |
| Predicate | componentDesignationCode |
P75661
|
FINISHED |
| Object | 00128 |
—
|
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: 00128 | Statement: [USBMR1400128, componentDesignationCode, 00128]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentDesignationCode Context triple: [USBMR1400128, componentDesignationCode, 00128]
-
A.
manufacturerDesignation
Indicates that a specific designation, code, or model identifier has been assigned by the manufacturer to the referenced product or item.
-
B.
systemDesignation
Indicates that an entity has been assigned a specific formal label or identifier within a defined system or framework.
-
C.
designatorType
Indicates the specific role or category of a designator used to identify or reference an entity within a system or context.
-
D.
vendorDesignation
Indicates that one entity assigns or recognizes a specific vendor status, label, or role for another entity within a business or procurement context.
-
E.
hasInternalDesignationFor
chosen
Indicates that one entity assigns or uses an internal label, code, or designation to refer to another entity.
- 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 29, 2026, 9:15 p.m.