Triple
T9806627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth–Moon system |
E237968
|
entity |
| Predicate | moonRotationState |
P59573
|
FINISHED |
| Object | tidally locked to Earth |
—
|
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: tidally locked to Earth | Statement: [Earth–Moon system, moonRotationState, tidally locked to Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moonRotationState Context triple: [Earth–Moon system, moonRotationState, tidally locked to Earth]
-
A.
astronomicalPhase
Indicates the specific stage or phase an astronomical object (such as a planet or moon) is in within its cyclical progression as observed over time.
-
B.
isMoonOf
Indicates that one celestial body is a natural satellite orbiting another body, typically a planet or dwarf planet.
-
C.
isTidallyLockedTo
chosen
Indicates that one object's rotational period matches its orbital period around another object, so the same side always faces that other object.
-
D.
isOneOfMoonsOf
Indicates that the subject entity is one of the natural satellites (moons) that orbit the object entity.
-
E.
hasRotationPeriod
Indicates that one entity has a specified duration for completing a full rotation around its own axis.
- 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.