Triple
T35538289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIMONIC |
E1026991
|
entity |
| Predicate | typicalAlloyingElement |
—
|
GENERATED |
| Object | chromium |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAlloyingElement Context triple: [NIMONIC, typicalAlloyingElement, chromium]
-
A.
commonAlloyName
Indicates that one entity is the commonly used or recognized alloy name corresponding to another entity representing that alloy.
-
B.
formsAlloysWith
chosen
Indicates that two substances can combine to form a homogeneous metallic alloy with each other.
-
C.
typicalValueForMetals
Indicates the characteristic or commonly observed value of a given property specifically for metals.
-
D.
typicalValueForAluminum
Indicates the standard or commonly accepted value (such as a property or parameter) that is characteristic for aluminum in a given context.
-
E.
associatedMetal
Indicates a relationship where one entity is linked or connected to a particular metal, such as by composition, usage, origin, or symbolic association.
- F. None of above.
Provenance (1 batch)
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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.