Triple

T15522103
Position Surface form Disambiguated ID Type / Status
Subject nitrogen-15 E368992 entity
Predicate relativeAtomicMass P65741 FINISHED
Object 15.000108898 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: 15.000108898 | Statement: [nitrogen-15, relativeAtomicMass, 15.000108898]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relativeAtomicMass
Context triple: [nitrogen-15, relativeAtomicMass, 15.000108898]
  • A. atomicMass chosen
    Indicates the quantitative relationship specifying the mass of an atom (or isotope) of an element, typically expressed in atomic mass units.
  • 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. hasAtomicRadius
    Indicates that an entity possesses a specific atomic radius value, representing the size of its atoms.
  • 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. hasMassNumber
    Indicates that an atomic nucleus or isotope is associated with a specific mass number, representing the total count of protons and neutrons it contains.
  • 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_69d85a1794cc8190b0b428716296e63e completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0403543188190abac49d2b9decb89 completed April 16, 2026, 1:49 a.m.
PD Predicate disambiguation batch_69ded28ab0588190a47a9090d1238707 completed April 14, 2026, 11:49 p.m.
Created at: April 10, 2026, 4:04 a.m.