Triple
T33566929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GRS80 |
E859784
|
entity |
| Predicate | geocentricGravitationalConstant |
P176891
|
FINISHED |
| Object | 3.986005e14 m^3/s^2 |
—
|
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: 3.986005e14 m^3/s^2 | Statement: [GRS80, geocentricGravitationalConstant, 3.986005e14 m^3/s^2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geocentricGravitationalConstant Context triple: [GRS80, geocentricGravitationalConstant, 3.986005e14 m^3/s^2]
-
A.
centralBody
Indicates that one object serves as the primary gravitational or reference body around which another object orbits or is defined.
-
B.
equatorialGravity
Indicates the strength or value of gravitational acceleration measured at an object's equator.
-
C.
meanSurfaceGravity_m_per_s2
Indicates the average gravitational acceleration experienced at the surface of an object, measured in meters per second squared.
-
D.
gravityOfBody
Indicates the gravitational influence or field produced by a specific celestial body.
-
E.
usesSymbolForGravitationalConstant
Indicates that an entity adopts a particular symbol to represent the gravitational constant in formulas or notation.
- 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f70b0ca081908b24a98937e6ef66 |
completed | May 3, 2026, 7:19 a.m. |
Created at: May 1, 2026, 1:40 a.m.