Triple
T6939042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bohr radius |
E160625
|
entity |
| Predicate | approximateValueAngstrom |
P74396
|
FINISHED |
| Object | 0.529 Å |
—
|
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: 0.529 Å | Statement: [Bohr radius, approximateValueAngstrom, 0.529 Å]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateValueAngstrom Context triple: [Bohr radius, approximateValueAngstrom, 0.529 Å]
-
A.
approximateLengthInMeters
Indicates the estimated or roughly measured length of something expressed in meters.
-
B.
hasAtomicRadius
Indicates that an entity possesses a specific atomic radius value, representing the size of its atoms.
-
C.
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.
-
D.
approximateRadius
Indicates that one entity specifies or provides an estimated value for the radius of another entity.
-
E.
hasApproximateElectronDensity
Indicates that one entity possesses an electron density value that is close to, but not exactly equal to, that of another entity or reference.
- 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_69c6884f3db4819080ad65da69386206 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e0c74fe48190aeaa018631e52ef6 |
completed | March 27, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bd5a388190a57a96d925696ff6 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6e0c620f0819080e0ec49b36d4c30 |
completed | March 27, 2026, 7:55 p.m. |
Created at: March 27, 2026, 2:28 p.m.