Triple
T982922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth rotation |
E21210
|
entity |
| Predicate | siderealDayLength |
P2026
|
FINISHED |
| Object | 23 hours 56 minutes 4 seconds |
—
|
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: 23 hours 56 minutes 4 seconds | Statement: [Earth rotation, siderealDayLength, 23 hours 56 minutes 4 seconds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siderealDayLength Context triple: [Earth rotation, siderealDayLength, 23 hours 56 minutes 4 seconds]
-
A.
hasSolarDayLength
Indicates that an entity is associated with a specific duration for one complete solar day (the time between successive noons).
-
B.
dayLengthCharacteristic
Indicates a relationship where an entity is characterized or defined by the length or duration of its day.
-
C.
hasAverageYearLength
Indicates that one entity has a specified average duration for its year (orbital period), typically measured over time.
-
D.
hasRotationPeriod
chosen
Indicates that one entity has a specified duration for completing a full rotation around its own axis.
-
E.
hasOrbitalPeriod
Indicates that one entity completes a full orbit around another entity within a specified duration.
- 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_69a493c383dc8190a03257f22d4b4183 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b49284ac8190b1d7c828d728893c |
completed | March 1, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69a4b2aa219081908a6b0ef786b4aa52 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.