Triple

T25031111
Position Surface form Disambiguated ID Type / Status
Subject uranium-235 E626843 entity
Predicate oxidationStatesInCompounds P157564 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: [uranium-235, oxidationStatesInCompounds, +4]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: oxidationStatesInCompounds
Context triple: [uranium-235, oxidationStatesInCompounds, +4]
  • A. 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.
  • B. hasFormalOxidationStateOfMetal
    Indicates that a metal entity is assigned a specific formal oxidation state in a chemical context.
  • C. hasTypicalOxidationState
    Indicates that an element or species is associated with a commonly observed or characteristic oxidation state under standard or typical conditions.
  • D. mostStableOxidationState
    Indicates the oxidation state in which an element most commonly or preferentially exists under standard or typical conditions.
  • E. predominantOxidationStateInSolution
    Indicates the oxidation state that a chemical species most commonly or primarily adopts when present in a given solution.
  • 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_69e2ff2a2c088190be513727ee8bfe78 completed April 18, 2026, 3:48 a.m.
NER Named-entity recognition batch_69f44f6fcab081909470c94a5f519d79 completed May 1, 2026, 7 a.m.
PD Predicate disambiguation batch_69f442c0c2e88190acd7f170f10ccef6 completed May 1, 2026, 6:05 a.m.
PDg Predicate description generation batch_69f448fe11f08190bdd53ca7ba2d51e4 completed May 1, 2026, 6:32 a.m.
Created at: April 18, 2026, 6:07 a.m.