Triple
T35859475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryloth |
E1036905
|
entity |
| Predicate | orbitalCharacteristics |
P58578
|
FINISHED |
| Object | tidally locked to its star |
—
|
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 its star | Statement: [Ryloth, orbitalCharacteristics, tidally locked to its star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitalCharacteristics Context triple: [Ryloth, orbitalCharacteristics, tidally locked to its star]
-
A.
hasOrbitalCharacteristic
chosen
Indicates that an entity possesses a specific property or feature related to its orbit, such as shape, period, inclination, or other orbital parameters.
-
B.
orbitalEccentricity
Indicates the degree to which an orbit deviates from a perfect circle, quantifying how elongated the orbital path is.
-
C.
orbitType
Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
-
D.
hasOrbitalPeriod
Indicates that one entity completes a full orbit around another entity within a specified duration.
-
E.
astronomicalCharacteristic
Indicates that one entity has a specific astronomical property, feature, or attribute in relation to 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3883d48190b05e3d2da7a017ae |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.