Triple
T35538283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIMONIC |
E1026991
|
entity |
| Predicate | hasAlloyVariant |
P195370
|
FINISHED |
| Object | NIMONIC 75 |
—
|
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: NIMONIC 75 | Statement: [NIMONIC, hasAlloyVariant, NIMONIC 75]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlloyVariant Context triple: [NIMONIC, hasAlloyVariant, NIMONIC 75]
-
A.
hasVariant
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
B.
hasVariantsIn
Indicates that an entity exists in multiple alternative forms or versions within a specified context or set.
-
C.
hasCommercialVariant
Indicates that an entity has a related version that is produced, marketed, or sold commercially.
-
D.
hasVariantSeries
Indicates a relationship where one entity is a variant or alternative series derived from or associated with another series.
-
E.
hasVariantIngredient
Indicates that one ingredient is an alternative or substitute form of another ingredient used in a product or formulation.
- F. None of above. chosen
Provenance (4 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_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69fdbc5da9988190b95234bce4cc2062 |
completed | May 8, 2026, 10:35 a.m. |
Created at: May 3, 2026, 4:04 p.m.