Triple
T4542735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | seaborgium |
E107572
|
entity |
| Predicate | atomicWeight |
P5748
|
FINISHED |
| Object | [269] |
—
|
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: [269] | Statement: [seaborgium, atomicWeight, [269]]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: atomicWeight Context triple: [seaborgium, atomicWeight, [269]]
-
A.
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.
-
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.
hasAtomicRadius
Indicates that an entity possesses a specific atomic radius value, representing the size of its atoms.
-
D.
atomicRadiusPm
Indicates the size of an atom’s radius, measured in picometers, typically representing the distance from the nucleus to the outer boundary of its electron cloud.
-
E.
hasMassNumber
chosen
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_69bd43f922788190b7edfa294e39b178 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57d3be988190bf118c4a87415613 |
completed | March 20, 2026, 2:21 p.m. |
| PD | Predicate disambiguation | batch_69bd5220e40481908ca2d7e2c43d8531 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:05 p.m.