Triple
T36803396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berkelium |
E909379
|
entity |
| Predicate | covalentRadiusPm |
P186314
|
FINISHED |
| Object | 96 |
—
|
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: 96 | Statement: [Berkelium, covalentRadiusPm, 96]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: covalentRadiusPm Context triple: [Berkelium, covalentRadiusPm, 96]
-
A.
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.
-
B.
hasAtomicRadius
Indicates that an entity possesses a specific atomic radius value, representing the size of its atoms.
-
C.
approximateValueAngstrom
Indicates that one entity specifies an estimated or approximate value, measured in angstroms, for another entity.
-
D.
atomicMass
Indicates the quantitative relationship specifying the mass of an atom (or isotope) of an element, typically expressed in atomic mass units.
-
E.
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.
- 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_69f76e7b98888190899b6478a82ad6ae |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7cabdd2d88190be1c8de7e499cb83 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7ca91f1808190b2a05c4b691da0bb |
completed | May 3, 2026, 10:22 p.m. |
Created at: May 3, 2026, 4:12 p.m.