Triple
T10212003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSIRIS-REx |
E242350
|
entity |
| Predicate | bennuType |
P60174
|
FINISHED |
| Object | B-type 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: B-type asteroid | Statement: [OSIRIS-REx, bennuType, B-type asteroid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bennuType Context triple: [OSIRIS-REx, bennuType, B-type asteroid]
-
A.
systemHasInnerAsteroidBelt
Indicates that a planetary system contains an asteroid belt located in its inner region, closer to the central star than any outer belts.
-
B.
orbitalBodyType
chosen
Indicates the classification of an orbital body in terms of its type (e.g., planet, moon, asteroid, comet) within an orbital system.
-
C.
recognizedAsDwarfPlanetBy
Indicates that one entity is classified or acknowledged as a dwarf planet by a specified authority, organization, or source.
-
D.
BlueCometType
Indicates that an entity is classified as a Blue Comet, specifying that it belongs to the category or type denoted by "BlueComet."
-
E.
debrisDiskType
Indicates the specific classification or subtype of a debris disk associated with an astronomical object.
- 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_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. |
Created at: April 6, 2026, 11:02 a.m.