Triple
T11078387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble sequence of galaxy classification |
E261924
|
entity |
| Predicate | ordersGalaxiesBy |
P97086
|
FINISHED |
| Object | bulge-to-disk ratio |
—
|
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: bulge-to-disk ratio | Statement: [Hubble sequence of galaxy classification, ordersGalaxiesBy, bulge-to-disk ratio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ordersGalaxiesBy Context triple: [Hubble sequence of galaxy classification, ordersGalaxiesBy, bulge-to-disk ratio]
-
A.
containsGalaxy
Indicates that one entity spatially includes or encompasses a galaxy as part of its contents or structure.
-
B.
hostGalaxyConstellation
Indicates the constellation in which the host galaxy of an object is located.
-
C.
targetGalaxy
Indicates that one entity is the galaxy toward which another entity is directed, aimed, or focused.
-
D.
isSatelliteGalaxyOf
Indicates that one galaxy orbits and is gravitationally bound to another, larger host galaxy as its satellite.
-
E.
galacticDestination
Indicates that one entity serves as the target or endpoint location within a galaxy that another entity is directed or traveling toward.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799953d58819096b645a1377e70f2 |
completed | April 9, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_69d74415403c81909778bcd829e8832e |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750ca52ec8190a559432a5de106fd |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:27 p.m.