Triple
T37418595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milky Way bulge and bar |
E929784
|
entity |
| Predicate | hasBulgeMass |
P193510
|
FINISHED |
| Object | of order 10^10 solar masses |
—
|
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: of order 10^10 solar masses | Statement: [Milky Way bulge and bar, hasBulgeMass, of order 10^10 solar masses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBulgeMass Context triple: [Milky Way bulge and bar, hasBulgeMass, of order 10^10 solar masses]
-
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.
hasBulgeToDiskRatio
Indicates the proportional relationship between the size or luminosity of a galaxy’s central bulge and its surrounding disk.
-
D.
bulge
Indicates that one entity protrudes outward or swells relative to another reference surface or boundary.
-
E.
hasCentralBulge
Indicates that an astronomical object, typically a galaxy, possesses a dense, rounded central concentration of stars or matter.
- 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_69f76ebde49481908566cd96b37ccc84 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69fd485e0c20819099756b4fe39ac326 |
completed | May 8, 2026, 2:20 a.m. |
Created at: May 3, 2026, 4:16 p.m.