Triple
T36574046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E0 elliptical galaxy |
E902195
|
entity |
| Predicate | hasBulgeToDiskRatio |
P192330
|
FINISHED |
| Object | no disk component |
—
|
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 disk component | Statement: [E0 elliptical galaxy, hasBulgeToDiskRatio, no disk component]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBulgeToDiskRatio Context triple: [E0 elliptical galaxy, hasBulgeToDiskRatio, no disk component]
-
A.
hasBulge
Indicates that one entity possesses or exhibits a protruding or swollen part relative to its surrounding surface or structure.
-
B.
hasBulgeType
Indicates the specific kind or classification of bulge associated with an entity.
-
C.
hasCentralBulge
Indicates that an astronomical object, typically a galaxy, possesses a dense, rounded central concentration of stars or matter.
-
D.
hasGasToStellarMassRatio
Indicates the proportion between an object's gas mass and its stellar mass.
-
E.
isStarburstGalaxy
Indicates that a galaxy exhibits the intense, short-lived burst of star formation characteristic of a starburst galaxy.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
| PDg | Predicate description generation | batch_69fd05b965608190a3666410b9f8e125 |
completed | May 7, 2026, 9:35 p.m. |
Created at: May 3, 2026, 4:11 p.m.