Triple
T6939033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bohr radius |
E160625
|
entity |
| Predicate | mostProbableRadiusRelation |
P23277
|
FINISHED |
| Object | r_mp(1s hydrogen) = a₀ |
—
|
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: r_mp(1s hydrogen) = a₀ | Statement: [Bohr radius, mostProbableRadiusRelation, r_mp(1s hydrogen) = a₀]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mostProbableRadiusRelation Context triple: [Bohr radius, mostProbableRadiusRelation, r_mp(1s hydrogen) = a₀]
-
A.
approximateRadius
chosen
Indicates that one entity specifies or provides an estimated value for the radius of another entity.
-
B.
hasMeanRadius
Indicates that an entity possesses a specified average radius measurement, typically representing the mean distance from its center to its surface.
-
C.
possibleRelative
Indicates a relationship where one entity may be related to another by family or kinship, but the exact nature of the relationship is uncertain or not fully established.
-
D.
polarRadius_km
Indicates the length of an object's radius from its center to a pole, measured in kilometers.
-
E.
valueRelation
Indicates a comparative or associative relationship between the values or magnitudes of two or more entities.
- 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_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. |
Created at: March 27, 2026, 2:28 p.m.