Triple
T9806637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth–Moon system |
E237968
|
entity |
| Predicate | hasPrecessionPeriod_years |
P27812
|
FINISHED |
| Object | about 18.6 |
—
|
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 18.6 | Statement: [Earth–Moon system, hasPrecessionPeriod_years, about 18.6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrecessionPeriod_years Context triple: [Earth–Moon system, hasPrecessionPeriod_years, about 18.6]
-
A.
nodePrecessionPeriod
chosen
Indicates the duration of time it takes for the line of nodes of an orbit to complete one full precessional cycle relative to a reference frame.
-
B.
hasObliquityPeriod
Indicates the relationship between an object and the duration of its axial tilt (obliquity) cycle.
-
C.
hasOrbitalPeriod
Indicates that one entity completes a full orbit around another entity within a specified duration.
-
D.
accuracyComparedToTropicalYear
Indicates how closely something’s measured or defined duration matches the length of a tropical year.
-
E.
driftPerYearRelativeToTropicalYearDays
Indicates the amount of calendar drift, measured in days per year, relative to the length of the tropical year.
- 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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdab7cb9588190953a063cb7b9e29e |
completed | April 1, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03dd2da881909052fbf29736a773 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:29 p.m.