Triple
T13690137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carme |
E328238
|
entity |
| Predicate | progradeOrRetrograde |
P45906
|
FINISHED |
| Object | retrograde |
—
|
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: retrograde | Statement: [Carme, progradeOrRetrograde, retrograde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: progradeOrRetrograde Context triple: [Carme, progradeOrRetrograde, retrograde]
-
A.
hasOrbitalDirection
chosen
Indicates that one celestial body orbits another in a specified directional sense (e.g., prograde or retrograde).
-
B.
ageProgressionDirection
Indicates the direction in which an entity’s age changes over time within a given process or representation (e.g., from younger to older or older to younger).
-
C.
isOrbital
Indicates that one entity moves in a curved, repeating path around another entity due to gravitational or similar central forces.
-
D.
isOrbitalTo
Indicates that one entity moves in a curved, repeating path around another entity under the influence of a central force, typically gravity.
-
E.
isInDirectionOf
Indicates that one entity is oriented or positioned toward the direction in which another entity lies.
- 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.