Triple
T11000544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun-synchronous orbit |
E259991
|
entity |
| Predicate | usesEarthOblateness |
P96575
|
FINISHED |
| Object | J2 perturbation causes nodal precession |
—
|
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: J2 perturbation causes nodal precession | Statement: [Sun-synchronous orbit, usesEarthOblateness, J2 perturbation causes nodal precession]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesEarthOblateness Context triple: [Sun-synchronous orbit, usesEarthOblateness, J2 perturbation causes nodal precession]
-
A.
hasEquatorialCircumference
Indicates that one entity has a specified measurement for its circumference at the equator.
-
B.
equatorialGravity
Indicates the strength or value of gravitational acceleration measured at an object's equator.
-
C.
forEarthApprox
Indicates an approximate or estimated value or condition as it pertains to Earth or an Earth-related context.
-
D.
hasEquatorialRadius
Indicates that an entity has a specified radius measured at its equator.
-
E.
inclinationToEarthEquator
Indicates the angle between an object's orbital or rotational plane and Earth's equatorial plane.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d796d68b608190a8d016b9383e82f8 |
completed | April 9, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69d72e93ac648190b46c5d12bf3eb1e9 |
completed | April 9, 2026, 4:44 a.m. |
| PDg | Predicate description generation | batch_69d732242fdc8190be77d1f730a42935 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:25 p.m.