Triple
T5683826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ursa Minor Dwarf Galaxy |
E125261
|
entity |
| Predicate | orbitalRelation |
P11957
|
FINISHED |
| Object | orbits Milky Way |
—
|
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: orbits Milky Way | Statement: [Ursa Minor Dwarf Galaxy, orbitalRelation, orbits Milky Way]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitalRelation Context triple: [Ursa Minor Dwarf Galaxy, orbitalRelation, orbits Milky Way]
-
A.
orbitalAssociation
Indicates a relationship in which one object is gravitationally bound to and moves in an orbit around another object.
-
B.
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.
-
C.
relatedAstronomicalObject
Indicates that one astronomical object has a specified relationship or association with another astronomical object.
-
D.
orbitType
Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
-
E.
orbitedBody
chosen
Indicates that one object moves in a path around another object due to gravitational or similar orbital forces.
- 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_69c0082a884c8190a79001bae658941f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0248751bc8190b12aaa42d1ef17e3 |
completed | March 22, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69c021be59088190a81c880957f666ab |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.