Triple
T33212159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSIRIS-APEX |
E850189
|
entity |
| Predicate | targetDynamicalClass |
P17318
|
FINISHED |
| Object | Aten asteroid |
—
|
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: Aten asteroid | Statement: [OSIRIS-APEX, targetDynamicalClass, Aten asteroid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetDynamicalClass Context triple: [OSIRIS-APEX, targetDynamicalClass, Aten asteroid]
-
A.
destinationClass
Indicates the class or category that serves as the target or endpoint of a relationship or transition from another entity.
-
B.
hasDynamicalClass
chosen
Indicates that an entity belongs to a specific category defined by its dynamical or motion-related behavior (e.g., orbital or kinematic characteristics).
-
C.
designatedClass
Indicates that one entity is formally assigned or specified as the class or category to which another entity belongs.
-
D.
topClassOf
Indicates that one class is the most general or highest-level superclass from which another class (or set of classes) ultimately derives.
-
E.
laterClass
Indicates that one class occurs or is scheduled at a time later than another class.
- 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_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
Created at: May 1, 2026, 1:30 a.m.