Triple
T7272871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tau Ceti f |
E161147
|
entity |
| Predicate | hostStarSpectralClass |
P42135
|
FINISHED |
| Object | G-type main-sequence star |
—
|
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: G-type main-sequence star | Statement: [Tau Ceti f, hostStarSpectralClass, G-type main-sequence star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostStarSpectralClass Context triple: [Tau Ceti f, hostStarSpectralClass, G-type main-sequence star]
-
A.
spectralClass
Indicates the classification of an astronomical object based on the characteristics of its spectrum, such as temperature and spectral features.
-
B.
dominantSpectralType
Indicates the primary or most prevalent spectral type characterizing the electromagnetic emission of an object or region.
-
C.
hostStarType
chosen
Indicates the classification of the star that serves as the primary host for an object, such as a planet or planetary system.
-
D.
starType
Indicates the classification relationship specifying what type or category of star an astronomical object is.
-
E.
hasStellarSpectrum
Indicates that an astronomical object exhibits a particular stellar spectrum characterizing its emitted light across wavelengths.
- 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_69c6885181008190b419040e22939c7c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb8a0b4881908ff27c5a75bd4a95 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76a84a081908d4184c55b728e48 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:58 p.m.