Triple
T7581803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milankovitch cycles |
E179504
|
entity |
| Predicate | hasObliquityPeriod |
P77988
|
FINISHED |
| Object | about 41,000 years |
—
|
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 41,000 years | Statement: [Milankovitch cycles, hasObliquityPeriod, about 41,000 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasObliquityPeriod Context triple: [Milankovitch cycles, hasObliquityPeriod, about 41,000 years]
-
A.
obliquityOfOrbit
Indicates the angle between an object's orbital plane and a reference plane, describing how tilted the orbit is relative to that reference.
-
B.
hasOrbitalPeriod
Indicates that one entity completes a full orbit around another entity within a specified duration.
-
C.
hasAxialTilt
Indicates that one celestial body’s rotational axis is tilted at a certain angle relative to its orbital plane around another body.
-
D.
hasEquinox
Indicates that an astronomical object or system possesses one or more equinox points or events in its orbital or rotational cycle.
-
E.
hasAverageYearLength
Indicates that one entity has a specified average duration for its year (orbital period), typically measured over time.
- 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_69c69f327db881909a21ae3b156f8ded |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f978341081909e009c410ffc5039 |
completed | March 27, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e04c2c8190a889d928515d9b8e |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8184bb08190b2f70545a6aa277c |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:52 p.m.