Triple
T19260560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pluto’s satellite system |
E481636
|
entity |
| Predicate | hasPrimaryTidalLocking |
P60177
|
FINISHED |
| Object | Pluto–Charon mutually tidally locked |
—
|
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: Pluto–Charon mutually tidally locked | Statement: [Pluto’s satellite system, hasPrimaryTidalLocking, Pluto–Charon mutually tidally locked]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryTidalLocking Context triple: [Pluto’s satellite system, hasPrimaryTidalLocking, Pluto–Charon mutually tidally locked]
-
A.
isTidallyLockedWith
chosen
Indicates that two astronomical bodies always show the same face to each other because one’s rotation period matches its orbital period around the other.
-
B.
isTidallyLockedTo
Indicates that one object's rotational period matches its orbital period around another object, so the same side always faces that other object.
-
C.
likelyTidalLocking
Indicates that one astronomical body is likely gravitationally locked so that the same side always faces another body.
-
D.
hasAxialTilt
Indicates that one celestial body’s rotational axis is tilted at a certain angle relative to its orbital plane around another body.
-
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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb890e7c8190beba407f63459382 |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:28 p.m.