Triple
T33211876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSIRIS-REx |
E850182
|
entity |
| Predicate | relatedAsteroid |
P29786
|
FINISHED |
| Object | 99942 Apophis |
E850190
|
NE 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: 99942 Apophis | Statement: [OSIRIS-REx, relatedAsteroid, 99942 Apophis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedAsteroid Context triple: [OSIRIS-REx, relatedAsteroid, 99942 Apophis]
-
A.
relatedAstronomicalObject
chosen
Indicates that one astronomical object has a specified relationship or association with another astronomical object.
-
B.
associatedPlanet
Indicates a relationship where one entity is linked or connected to a particular planet, typically as its relevant or corresponding planetary body.
-
C.
relatedConstellation
Indicates a relationship where one entity is associated with, connected to, or corresponds to a particular constellation.
-
D.
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.
-
E.
hasOrbitalRelationship
Indicates that one entity is in an orbital relationship with another, such as revolving around or being gravitationally bound in a regular orbit.
- F. None of above.
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_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a352fca93608190ae8c69a5f7d47a61 |
completed | June 19, 2026, 12:02 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:30 a.m.