Triple
T27134609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ångström |
E681647
|
entity |
| Predicate | approximateAtomicRadiusScale |
P74396
|
FINISHED |
| Object | 1 ångström |
—
|
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: 1 ångström | Statement: [ångström, approximateAtomicRadiusScale, 1 ångström]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateAtomicRadiusScale Context triple: [ångström, approximateAtomicRadiusScale, 1 ångström]
-
A.
hasAtomicRadius
Indicates that an entity possesses a specific atomic radius value, representing the size of its atoms.
-
B.
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.
-
C.
approximateValueAngstrom
chosen
Indicates that one entity specifies an estimated or approximate value, measured in angstroms, for another entity.
-
D.
approximateRadius
Indicates that one entity specifies or provides an estimated value for the radius of another entity.
-
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.
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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 27, 2026, 9:06 a.m.