Triple
T36803277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | thorium |
E909377
|
entity |
| Predicate | primaryOxidationStateInCompounds |
P88861
|
FINISHED |
| Object | +4 |
—
|
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: +4 | Statement: [thorium, primaryOxidationStateInCompounds, +4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryOxidationStateInCompounds Context triple: [thorium, primaryOxidationStateInCompounds, +4]
-
A.
oxidationStatesInCompounds
Indicates the oxidation states that elements possess within specific chemical compounds.
-
B.
oxidationStates
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.
-
C.
mostStableOxidationState
chosen
Indicates the oxidation state in which an element most commonly or preferentially exists under standard or typical conditions.
-
D.
hasTypicalOxidationState
Indicates that an element or species is associated with a commonly observed or characteristic oxidation state under standard or typical conditions.
-
E.
hasFormalOxidationStateOfMetal
Indicates that a metal entity is assigned a specific formal oxidation state in a chemical context.
- 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_69f76e7b98888190899b6478a82ad6ae |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.