Triple
T23836109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saturnian system |
E590856
|
entity |
| Predicate | hasOrbitalResonancePhenomena |
P153798
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Saturnian system, hasOrbitalResonancePhenomena, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrbitalResonancePhenomena Context triple: [Saturnian system, hasOrbitalResonancePhenomena, yes]
-
A.
hasOrbitalResonanceWith
Indicates that two orbiting bodies have orbital periods in a simple integer ratio, causing their gravitational influences to repeat in a regular, synchronized pattern.
-
B.
hasOrbitalResonanceHistory
Indicates that there has been a past or present orbital resonance relationship between two celestial bodies or systems.
-
C.
hasOrbitalCharacteristic
Indicates that an entity possesses a specific property or feature related to its orbit, such as shape, period, inclination, or other orbital parameters.
-
D.
hasOrbitalPeriod
Indicates that one entity completes a full orbit around another entity within a specified duration.
-
E.
hasOrbitalStability
Indicates that an object maintains a stable, non-disruptive orbit around another body over time.
- F. None of above. chosen
Provenance (4 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_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c882f9148190bb28fe7566ef1e70 |
completed | April 29, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f158b0e320819090b947ee7eb14116 |
completed | April 29, 2026, 1:02 a.m. |
Created at: April 17, 2026, 8:07 p.m.