Triple
T32170022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth–Moon barycenter |
E821684
|
entity |
| Predicate | massRatioEarthToMoon |
P62429
|
FINISHED |
| Object | about 81.3 to 1 |
—
|
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: about 81.3 to 1 | Statement: [Earth–Moon barycenter, massRatioEarthToMoon, about 81.3 to 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: massRatioEarthToMoon Context triple: [Earth–Moon barycenter, massRatioEarthToMoon, about 81.3 to 1]
-
A.
earthToMoonRadiusRatio
Indicates the proportional relationship between the radius of the Earth and the radius of the Moon.
-
B.
massRelativeToMoon
chosen
Indicates that one entity’s mass is being expressed as a value relative to, or in comparison with, the mass of the Moon.
-
C.
moonMassFraction
Indicates the proportion of an object's total mass that is contained in its moon or moons.
-
D.
massRelativeToEarth
Indicates the comparative amount of mass an entity has relative to the mass of Earth.
-
E.
approximateSunMoonSizeRatio
Indicates the proportional relationship between the apparent sizes of the Sun and the Moon as observed from a given viewpoint.
- 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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba73aa9c819082328ddf6ec799ec |
completed | May 3, 2026, 3:01 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:33 a.m.