Triple
T32170026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth–Moon barycenter |
E821684
|
entity |
| Predicate | orbitsWithPeriod |
P2028
|
FINISHED |
| Object | about 27.3 days relative to stars |
—
|
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 27.3 days relative to stars | Statement: [Earth–Moon barycenter, orbitsWithPeriod, about 27.3 days relative to stars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitsWithPeriod Context triple: [Earth–Moon barycenter, orbitsWithPeriod, about 27.3 days relative to stars]
-
A.
hasOrbitalPeriod
chosen
Indicates that one entity completes a full orbit around another entity within a specified duration.
-
B.
orbits
Indicates that one object moves in a curved, usually repetitive path around another object due to a central force such as gravity.
-
C.
coOrbitsWith
Indicates that two celestial bodies share the same or closely related orbital path around a common central object.
-
D.
orbitsPerDay
Indicates the number of complete orbits an object makes around another object in a single day.
-
E.
orbitsEarth
Indicates that one object follows a gravitationally bound path around Earth as its primary central body.
- 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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba73aa9c819082328ddf6ec799ec |
completed | May 3, 2026, 3:01 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:33 a.m.