Triple
T14330121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ultium Cells |
E355322
|
entity |
| Predicate | usesChemistry |
P113995
|
FINISHED |
| Object | lithium-ion |
—
|
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: lithium-ion | Statement: [Ultium Cells, usesChemistry, lithium-ion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesChemistry Context triple: [Ultium Cells, usesChemistry, lithium-ion]
-
A.
usedInChemistry
Indicates that something is employed or applied within the context of chemistry, such as in chemical processes, experiments, or analyses.
-
B.
commonChemistry
Indicates that two entities share similar or related chemical properties, composition, or behavior.
-
C.
containsChemical
Indicates that one entity includes or has within it a specified chemical substance.
-
D.
keyChemicalDiscussed
Indicates that a particular chemical substance is a central topic of discussion in a given context or communication.
-
E.
chemicallyRelatedTo
Indicates a relationship where two entities are connected through a chemical association, such as sharing structural features, participating in related reactions, or being derivable from one another chemically.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8c1def0081908f03cda8e84d20c0 |
completed | April 14, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e9ded24819099200349cf80e068 |
completed | April 14, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:13 a.m.