Triple
T5007438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Styx |
E112530
|
entity |
| Predicate | tidallyLockedTo |
P59573
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [Styx, tidallyLockedTo, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tidallyLockedTo Context triple: [Styx, tidallyLockedTo, none]
-
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.
hasRotationPeriod
Indicates that one entity has a specified duration for completing a full rotation around its own axis.
-
D.
tidalLock
Indicates that one astronomical body always shows the same face to another because its rotational period matches its orbital period around that body.
-
E.
isNaturalSatelliteFeatureOf
Indicates that a physical feature (such as a crater, valley, or mountain) is located on and belongs to a specific natural satellite (e.g., a moon).
- 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_69bd4433d0b08190877e83959ef40d81 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd730a7590819088ab8d49c5c88c2f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714cbc448190aa53a8a83d768b64 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.