Triple
T13690097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jupiter XX |
E328237
|
entity |
| Predicate | orbitalCharacteristic |
P58578
|
FINISHED |
| Object | distant orbit |
—
|
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: distant orbit | Statement: [Jupiter XX, orbitalCharacteristic, distant orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitalCharacteristic Context triple: [Jupiter XX, orbitalCharacteristic, distant orbit]
-
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.
orbitType
Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
-
C.
astronomicalCharacteristic
Indicates that one entity has a specific astronomical property, feature, or attribute in relation to another entity.
-
D.
isOrbital
Indicates that one entity moves in a curved, repeating path around another entity due to gravitational or similar central forces.
-
E.
orbitalEccentricity
Indicates the degree to which an orbit deviates from a perfect circle, quantifying how elongated the orbital path is.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc6721c248190ac48491b5f39c8f0 |
completed | April 12, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.