Triple
T33211872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSIRIS-REx |
E850182
|
entity |
| Predicate | EarthGravityAssistDate |
P22034
|
FINISHED |
| Object | 2017-09-22 |
—
|
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: 2017-09-22 | Statement: [OSIRIS-REx, EarthGravityAssistDate, 2017-09-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EarthGravityAssistDate Context triple: [OSIRIS-REx, EarthGravityAssistDate, 2017-09-22]
-
A.
gravityAssistBody
Indicates that one body is used as the primary celestial object providing a gravitational assist to alter the trajectory or velocity of another body or spacecraft.
-
B.
spacecraftDestination
Indicates that a spacecraft is intended to travel to, arrive at, or be directed toward a particular destination.
-
C.
spaceStationReentryDate
Indicates the date on which a space station reenters the Earth's atmosphere or is deorbited.
-
D.
flybyDate
chosen
Indicates the date on which one object passes close to another in a flyby encounter.
-
E.
spaceDependence
Indicates a relationship where one entity’s properties, behavior, or validity depend on spatial position or configuration relative to another entity or reference frame.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:30 a.m.