Triple
T21071259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 4388 |
E519111
|
entity |
| Predicate | showsStrongEmissionLines |
P84901
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NGC 4388, showsStrongEmissionLines, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showsStrongEmissionLines Context triple: [NGC 4388, showsStrongEmissionLines, true]
-
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.
hasStrongMolecularBands
Indicates that the subject exhibits prominent, easily detectable absorption or emission features in its spectrum caused by molecular transitions.
-
D.
hasDominantLines
Indicates that one element in a pair exhibits stronger, more prominent, or controlling linear features relative to the other.
-
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_69e0b505ef108190b25dd4033e2ff7eb |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6feb8ed4481909c9f804ccd8da3e2 |
completed | April 21, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:46 p.m.