Triple
T35538225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monel |
E1026990
|
entity |
| Predicate | hasTypicalNickelContent |
P149158
|
FINISHED |
| Object | about 65 to 70 percent |
—
|
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: about 65 to 70 percent | Statement: [Monel, hasTypicalNickelContent, about 65 to 70 percent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalNickelContent Context triple: [Monel, hasTypicalNickelContent, about 65 to 70 percent]
-
A.
nickelComponentDerivedFrom
Indicates that a nickel-containing component originates from, or is obtained or produced based on, another specified source entity.
-
B.
metalContentPre1965
Indicates that something has the metal composition or standard that was used before the year 1965.
-
C.
chainMadeOf
Indicates that a chain is composed of, or constructed from, a specified material or substance.
-
D.
standardGoldContent
Indicates the specified standard or required amount of gold contained in something, typically as a measure of purity or value.
-
E.
typicalValueForMetals
chosen
Indicates the characteristic or commonly observed value of a given property specifically for metals.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff7fc835f08190afd1f8129b7a62a2 |
completed | May 9, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69ff7f2e99ac8190ba372a1358a05a30 |
completed | May 9, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.