Triple
T2171504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nobelium |
E48435
|
entity |
| Predicate | oxidationState |
P19722
|
FINISHED |
| Object | +2 |
—
|
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: +2 | Statement: [Nobelium, oxidationState, +2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oxidationState Context triple: [Nobelium, oxidationState, +2]
-
A.
oxidationStates
chosen
Indicates the specific oxidation numbers assigned to an element or atom within a chemical species, reflecting its electron loss or gain state in that context.
-
B.
standardAtomicWeight
Indicates the conventional average mass of atoms of an element in a specified sample, typically reflecting the weighted mean of its naturally occurring isotopes.
-
C.
oxidizer
Indicates a relationship where one entity acts as an oxidizing agent that accepts electrons from, or promotes the oxidation of, another entity in a chemical process.
-
D.
hasAtomicNumber
Indicates that one entity is the chemical element whose atomic number (number of protons in its nucleus) is given by the other entity.
-
E.
hasIonizationState
Indicates the specific ionization state or charge level that an entity (such as an atom or molecule) possesses.
- 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_69a88aa3faa48190995b233af6525815 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc1559ff481908efe3f214b2570dc |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbd9efc1c81909a65044a1ffc9038 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.