Triple
T37588662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gliese 581d |
E935193
|
entity |
| Predicate | tidalLockingStatus |
P27809
|
FINISHED |
| Object | possibly 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: possibly tidally locked | Statement: [Gliese 581d, tidalLockingStatus, possibly tidally locked]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tidalLockingStatus Context triple: [Gliese 581d, tidalLockingStatus, possibly tidally locked]
-
A.
tidalLock
chosen
Indicates that one astronomical body always shows the same face to another because its rotational period matches its orbital period around that body.
-
B.
hasLock
Indicates that one entity possesses or is secured by a lock associated with another entity.
-
C.
typeOfLock
Indicates the specific kind or category of lock mechanism associated with an entity.
-
D.
tokenStatus
Indicates the current state or condition of a token within a process, system, or lifecycle.
-
E.
usesLockSystem
Indicates that one entity employs or relies on a locking mechanism or lock-based system provided by another entity.
- 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_69f76ece61dc8190a0ab33f8d87d0a7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.