Triple
T19019896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpha Telescopii |
E465454
|
entity |
| Predicate | dominantSpectralLines |
P84901
|
FINISHED |
| Object | helium lines |
—
|
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: helium lines | Statement: [Alpha Telescopii, dominantSpectralLines, helium lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantSpectralLines Context triple: [Alpha Telescopii, dominantSpectralLines, helium lines]
-
A.
dominantEmissionLines
Indicates that the specified emission lines are the most intense or prominent spectral features in the observed emission from an object or region.
-
B.
hasSpectralLines
chosen
Indicates that one entity exhibits or is characterized by specific spectral lines associated with another entity.
-
C.
dominantSpectralType
Indicates the primary or most prevalent spectral type characterizing the electromagnetic emission of an object or region.
-
D.
spectroscopyElement
Indicates that an element is identified or analyzed through a spectroscopy measurement or observation.
-
E.
emitsSpectrum
Indicates that one entity produces or gives off electromagnetic radiation characterized by a particular spectrum.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6ddc9608190a1daec9ddcc79a7a |
completed | April 20, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.