Triple
T18484963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 2976 |
E451662
|
entity |
| Predicate | nucleusType |
P131835
|
FINISHED |
| Object | no strong active galactic nucleus |
—
|
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: no strong active galactic nucleus | Statement: [NGC 2976, nucleusType, no strong active galactic nucleus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nucleusType Context triple: [NGC 2976, nucleusType, no strong active galactic nucleus]
-
A.
isNucleusOf
Indicates that one entity functions as the central or most important core component of another entity.
-
B.
isNucleusOfIsotope
Indicates that a given nucleus belongs to and characterizes a specific isotope.
-
C.
nuclearProperty
Indicates a relationship where an entity possesses or is characterized by a specific nuclear-related attribute, such as structure, behavior, or interaction at the atomic nucleus level.
-
D.
cellType
Indicates the classification relationship that specifies what type of cell an entity is or is associated with.
-
E.
cellStructure
Indicates the structural organization, components, and physical arrangement that make up a cell.
- F. None of above. chosen
Provenance (4 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e531d6502c8190af167b954bf8e989 |
completed | April 19, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:35 a.m.