Triple
T35629854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asteroid belt |
E1029552
|
entity |
| Predicate | containsSpectralClass |
P84080
|
FINISHED |
| Object | C-type asteroids |
—
|
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: C-type asteroids | Statement: [Asteroid belt, containsSpectralClass, C-type asteroids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsSpectralClass Context triple: [Asteroid belt, containsSpectralClass, C-type asteroids]
-
A.
spectralClass
Indicates the classification of an astronomical object based on the characteristics of its spectrum, such as temperature and spectral features.
-
B.
hasStellarSpectrum
Indicates that an astronomical object exhibits a particular stellar spectrum characterizing its emitted light across wavelengths.
-
C.
spectralTypesPresent
chosen
Indicates that certain spectral types are present or occur within a given context or set of entities.
-
D.
hasSpectralTypeComponentA
Indicates that an entity (typically a star system) has a primary component A with the specified spectral type.
-
E.
spectralTypeACharacteristic
Indicates that an entity has a characteristic or property associated with spectral type A (e.g., typical of A-type spectra).
- 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00c9ddd62881909859a36b114a4132 |
completed | May 10, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_6a00c939b88881909d5353db4265e572 |
completed | May 10, 2026, 6:06 p.m. |
Created at: May 3, 2026, 4:05 p.m.