Triple

T3921517
Position Surface form Disambiguated ID Type / Status
Subject Fermium E88968 entity
Predicate hasPositionInPeriodicTable P37375 FINISHED
Object between einsteinium and mendelevium 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: between einsteinium and mendelevium | Statement: [Fermium, hasPositionInPeriodicTable, between einsteinium and mendelevium]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPositionInPeriodicTable
Context triple: [Fermium, hasPositionInPeriodicTable, between einsteinium and mendelevium]
  • A. positionInPeriodicTable chosen
    Indicates the placement or location of a chemical element within the structure of the periodic table.
  • B. hasAtomicNumber
    Indicates that one entity is the chemical element whose atomic number (number of protons in its nucleus) is given by the other entity.
  • C. hasProtonNumber
    Indicates that an entity (typically a chemical element or atom) possesses a specific number of protons in its nucleus.
  • D. hasElectronConfiguration
    Indicates that an entity (typically an atom or ion) possesses a specific arrangement of electrons in its atomic orbitals.
  • E. hasNeutronNumber
    Indicates that an entity (typically an atom or nuclide) has a specified number of neutrons in its nucleus.
  • 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_69aed955229881909e85e73ffab1d343 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aef188b474819087680db42b04ecdd completed March 9, 2026, 4:12 p.m.
PD Predicate disambiguation batch_69aee75eedcc81908088ff4dbb8be56b completed March 9, 2026, 3:29 p.m.
Created at: March 9, 2026, 3:22 p.m.