Triple
T25637997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adrastea |
E642758
|
entity |
| Predicate | isTidalLockedTo |
P59573
|
FINISHED |
| Object | Jupiter |
—
|
NE NERFINISHED |
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: Jupiter | Statement: [Adrastea, isTidalLockedTo, Jupiter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTidalLockedTo Context triple: [Adrastea, isTidalLockedTo, Jupiter]
-
A.
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.
-
B.
isTidallyLockedWith
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.
-
C.
likelyTidalLocking
Indicates that one astronomical body is likely gravitationally locked so that the same side always faces another body.
-
D.
hasRotationPeriod
Indicates that one entity has a specified duration for completing a full rotation around its own axis.
-
E.
isTidalInteractionSuspected
Indicates that a gravitational interaction between astronomical bodies is suspected to be causing observable tidal effects or disturbances.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa6345548190a52498ecb0a2f555 |
completed | May 2, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 5:36 p.m.