Triple
T10212004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSIRIS-REx |
E242350
|
entity |
| Predicate | bennuOrbitClass |
P92735
|
FINISHED |
| Object | Apollo 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: Apollo asteroid | Statement: [OSIRIS-REx, bennuOrbitClass, Apollo asteroid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bennuOrbitClass Context triple: [OSIRIS-REx, bennuOrbitClass, Apollo asteroid]
-
A.
orbitsBarycenterOf
Indicates that one object follows an orbital path around the shared center of mass (barycenter) of another system or group of objects.
-
B.
orbitalEccentricity
Indicates the degree to which an orbit deviates from a perfect circle, quantifying how elongated the orbital path is.
-
C.
hasOrbitalPeriod
Indicates that one entity completes a full orbit around another entity within a specified duration.
-
D.
solarOrbitName
Indicates that an entity is the designated name of the orbit or orbital path of a solar system body.
-
E.
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.
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d3aa23bce881909b5deac612ec22cb |
completed | April 6, 2026, 12:42 p.m. |
| PD | Predicate disambiguation | batch_69d39559e5ac8190b88eca75956b7e6a |
completed | April 6, 2026, 11:13 a.m. |
| PDg | Predicate description generation | batch_69d3aa208c248190a0fb186b106389f3 |
completed | April 6, 2026, 12:42 p.m. |
Created at: April 6, 2026, 11:02 a.m.