Triple
T33212176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSIRIS-APEX |
E850189
|
entity |
| Predicate | plannedArrivalRelativeToFlyby |
P187068
|
FINISHED |
| Object | shortly after Apophis 2029 Earth flyby |
—
|
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: shortly after Apophis 2029 Earth flyby | Statement: [OSIRIS-APEX, plannedArrivalRelativeToFlyby, shortly after Apophis 2029 Earth flyby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedArrivalRelativeToFlyby Context triple: [OSIRIS-APEX, plannedArrivalRelativeToFlyby, shortly after Apophis 2029 Earth flyby]
-
A.
plannedArrivalBody
Indicates the celestial body or location at which an object or traveler is scheduled or intended to arrive.
-
B.
arrivalAtBennuDate
Indicates the date on which an entity arrives at the asteroid Bennu.
-
C.
flybyDate
Indicates the date on which one object passes close to another in a flyby encounter.
-
D.
arrivalSolOfOpportunity
Indicates the point in time or condition under which an opportunity becomes available or arrives at a particular solution or context.
-
E.
arrivalAt
Indicates the event or state of an entity reaching and being present at a specific destination or location.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb3424724c8190ba55ecf66fa0b171 |
completed | May 6, 2026, 12:29 p.m. |
Created at: May 1, 2026, 1:30 a.m.